Open source · MIT · Self-hosted

Your own private app cloud.

For you, your team, or your whole company.

Drop in a file or folder, or describe an app in plain words, and get a private web app you can share with a link. Every app is sandboxed. Sign in with built-in accounts from minute one, and switch on Microsoft Entra ID, Google Workspace or OIDC when your company is ready.

  • 1 Go binary
  • 1 data folder
  • 0 SSO required
A real recording, not a mock-up: drop a folder, it’s live, share it.

See it

This is what it looks like.

Real screenshots of Bunker running the code on GitHub today, with a made-up company’s data. No mock-ups.

Bunker home page: a greeting, a “Describe an app” box, a drop zone for files and folders, and cards for recent sites such as Q3 budget and Website launch.Bunker home page: a greeting, a “Describe an app” box, a drop zone for files and folders, and cards for recent sites such as Q3 budget and Website launch.

Everything you made, in one place

Drop a file or folder, describe an app, or start from a template. Recent sites, favorites and public links are right there.

Deploy in one click

Running in your cloud before your coffee cools.

Pick a button, wait a couple of minutes, open the URL and create your admin account. Bunker needs one machine and one real disk.

Any Linux server installs a hardened systemd service

curl -fsSL https://raw.githubusercontent.com/kucukkanat/bunker/master/install.sh | sudo BUNKER_URL=https://bunker.example.com sh

Docker data lives in one volume

docker run -p 8080:8080 -v bunker:/data ghcr.io/kucukkanat/bunker

On your laptop example apps, teammates and data in seconds

go install github.com/kucukkanat/bunker/cmd/bunker@latest && bunker demo

More options: Docker Compose with automatic HTTPS, Coolify, CapRover, Koyeb and Windows. All deploy guides →

Anything becomes an app

If it’s on your desktop, it can be an app.

Bunker looks at what you dropped and turns it into the right kind of page. Whoever you share it with opens a link and signs in.

  • .html

    A web page

    Published as it is. Links to popular CDN libraries are swapped for built-in copies.

  • folder · .zip

    A folder or zip

    Finds index.html, even inside dist/ or build/. Root paths keep working.

  • .jsx · .tsx

    React in one file

    A single component becomes a running app. Bunker bundles it for you. No build step.

  • .md

    Docs and notes

    Markdown becomes a clean, readable page. A folder becomes a docs site.

  • .md · slides: true

    Slides

    Split a Markdown file into slides with --- and present from the browser.

  • .csv · .xlsx

    A spreadsheet

    Becomes a table app: search, sort, filter, chart and export. Every sheet is a tab.

  • .ipynb

    A notebook

    Rendered with its charts and outputs, ready to read.

  • .pdf

    A PDF

    Opens in a built-in viewer that works inside the sandbox.

  • .png · .jpg · .mp4

    Images and video

    A tidy gallery page your team can browse.

  • plain words

    Describe it

    “A holiday tracker where managers approve requests.” The AI builds a draft, offers to fix any errors the preview shows, and you publish.

Sharewith people or groups, as viewer or editor
Ask for accessowners approve with one click
Every change is a versionrestore any of them
Draftspreview before anyone sees it
  • A backend when you need one

    Drop api/hello.js next to your pages and call it with bunker.fn. Run it on a schedule, after a change or from a webhook, with secrets and outbound fetch. Each call gets its own WebAssembly sandbox. No build step, no containers.

    Server functions →
  • Data from your other tools

    Power Automate, Zapier, a form or a nightly script can post JSON to a secret webhook URL. It lands in the app’s data and open pages update live.

    Inbound webhooks →
  • Public when you want it

    Share a portfolio or a page with friends, no accounts needed. Off until an admin allows it, and one switch closes every public link.

    Public links →
  • A builder that checks its work

    After each change the builder looks at the draft preview. If it shows an error, you get one click to have it fixed, before anyone else sees it.

    The AI builder →
  • Looks like you from the start

    One line of CSS gives an app Bunker’s fonts and clean light and dark styles, served by your own server, so even quick drafts look tidy without loading anything from the internet.

    The SDK and style kit →
  • Paste a GitHub link

    Paste a public repository (or one folder of it) on Home and it becomes a site: build output, a Markdown handbook or a folder of spreadsheets.

    Import from GitHub →
  • Email when you have it

    Point Bunker at any SMTP server and invites, password resets and notifications arrive by email. Without one, links are one click to copy.

    Email →
  • AI with nothing to configure

    Already exported ANTHROPIC_API_KEY or OPENAI_API_KEY? Bunker uses it. Running Ollama or LM Studio on the same machine? One click.

    AI providers →
  • On your phone’s home screen

    Add Bunker to a phone or laptop like an app. Every screen works at phone size, in light and dark, with a keyboard or a screen reader.

    Quickstart →

Or start from one of 16 templates

  • Requests & approvals
  • Team tracker
  • Sign-up sheet
  • Feedback
  • Quick poll
  • Dashboard
  • Directory & who’s out
  • Meeting notes
  • Equipment check-out
  • Room & desk booking
  • Inventory
  • Incident log
  • Onboarding checklist
  • Goals & OKRs
  • Kudos wall
  • Lunch orders

Each one is a real app with live data and sensible access rules. Change anything with the AI builder or the code editor. See them all →

Built for agents

Your coding agent already knows how to ship here.

Every button in Bunker is an API operation, and the CLI and MCP tools are generated from the same list. So whatever a person can do in the browser, an agent can do with that person’s permissions, and nothing more.

  • MCP with just the URL. Add https://bunker.corp.com/mcp to Claude, Cursor or ChatGPT. Sign-in happens through OAuth with your Bunker account.
  • Your apps, inside the chat. With MCP Apps, Claude, VS Code Copilot and Microsoft 365 Copilot can open a Bunker app right in the conversation. It runs as you, in the same sandbox, through a short-lived link.
  • A real CLI. bunker deploy, share, rollback, ai, api. Uploads only what changed. One binary, same as the server.
  • llms.txt. Agents read /llms.txt and learn the SDK, the sandbox rules and every operation.
  • Everything in the UI is in the API. Listed live at /api/v1/ops and /api/v1/openapi.json.

Connect your agent → · CLI reference →

Security, for IT and for you

Every app gets a locked room. You keep the keys.

An app is untrusted code written by a trusted coworker. Bunker treats it that way, with layers that each hold on their own.

  1. Sign-inBuilt-in accounts, or Entra ID, Google Workspace and OIDC. Only people you let in.
    1. BunkerChecks site, viewer and role on every call. Holds the session and every secret.
      1. App shellStrict CSP, script-src 'self'. Relays SDK calls from its own frame only.
        1. Sandboxed frameOpaque origin. Signed ticket URLs. No cookies, no storage, no internet.
          Your app’s code
  • An app can’t
  • Read the Bunker session or cookies
  • Open another app’s files or data
  • Call outside URLs, post forms, load CDNs
  • Hold API keys or tokens
  • Open popups or navigate the top window
  • Use camera, microphone, location or USB
  • Opaque-origin sandbox

    Every app runs in an iframe without allow-same-origin. It has no cookies, no storage and no reach into Bunker or other apps.

    sandbox="allow-scripts allow-forms allow-modals allow-downloads"
  • Signed content tickets

    App files are served under a short-lived HMAC ticket tied to the site, version and viewer. Revoke a share and the next request fails.

    /s/<site>/~r/<ticket>/index.html
  • No keys in pages

    Data, AI and Microsoft 365 calls go through the parent frame with the viewer’s session. Uploads containing API keys are refused at publish time.

    422 secret_detected
  • Connection-Allowlist

    CSP can’t stop WebRTC. On Chromium and Edge 152+ this header also blocks WebRTC, navigations and prefetch to anywhere but Bunker.

    Connection-Allowlist: (response-origin)
  • Viewer-scoped Microsoft 365

    An app sees SharePoint, Excel and OneDrive only with the viewer’s own rights, and only for scopes your admin allowed.

    delegated · admin allowlist
  • Audit everything

    Sign-ins, publishes, shares, views, data-rule and admin changes land in an indexed audit table, with every agent action marked as a token.

    site.share · site.view · auth.login
  • Sandboxed server code

    Server functions run in a fresh QuickJS-on-WebAssembly instance per call, with a memory cap, a time limit and the caller’s own rights. Admins choose where they may connect.

    64 MB · 30 s · outbound: internet | allowlist | off
  • SSRF-safe connections

    Apps reach internal APIs only through named connections an admin defines. Private and metadata addresses are blocked by default.

    bunker.connections.fetch("hr", { path: "/people" })
  • Your sign-in, your rules

    Built-in accounts use argon2id and one-time invite links. Company sign-in is single-tenant only, and Bunker refuses settings that would let personal accounts in.

    argon2id · tenant ≠ common

Read the threat model, including the risks that remain →

Small footprint

One binary. One folder. That’s the whole platform.

No Postgres, no Redis, no Kubernetes, no queue. Bunker is a pure-Go program with SQLite in WAL mode and a content-addressed file store. Files are compressed once at publish and served with ETags, so a small VM serves a big company.

  • Backups in one command. bunker backup takes a consistent snapshot while it runs; bunker restore puts it back.
  • Laptop-friendly. The first start on a desktop opens the setup page in your browser.
  • Tidy over time. Move someone’s sites when they leave, and archive apps nobody has opened for a while.
  • Upgrades are one click in Admin, with an automatic way back. Migrations run on start.
Requests per second
~30kon 4 cores
Memory when idle
~26 MBresident
Moving parts
1binary, no CGO
State
1folder to back up
Built for
5,000people per VM
Setup
~1 minfrom first start to your admin account

How it compares

The ease of a builder. The control of your own server.

CapabilityBunkerLow-code SaaSStatic hosting tools
Anyone can build: drop a file or describe it✓partly—
Runs on your own servers✓—varies
Company sign-in on every app, included✓paid tierextra setup
Share each app with people and groups✓✓—
Apps sandboxed from each other and the internet✓varies—
Database, files and live updates built in✓✓—
Server code, schedules and secrets, no extra service✓partly—
Agents deploy through CLI and MCP✓rarelypartly
Plain HTML you can take with you✓lock-in✓
Audit log✓paid tier—
Per-seat feesnoneper builder + per viewerusually none

Questions

Asked by IT, answered plainly.

Something missing? Ask on GitHub.

Do I need Microsoft 365 or SSO?

No. Bunker works out of the box with built-in accounts: you create the first admin in the setup page and invite people with one-time links. When you want company sign-in, switch on Microsoft Entra ID, Google Workspace or any OIDC provider, then turn built-in accounts off if you like.

Is it only for big companies?

No. Run it on a laptop or a five-dollar server for your own projects, share apps with a few friends or a small team, or put it in front of thousands of employees. Same binary.

Is Bunker ready for production?

Bunker is early and moving fast. Sign-in, sites, sharing, versions, the sandbox, the SDK, the AI builder, the CLI and MCP are in the code today. So are the dashboard, app types from Markdown to notebooks, templates, server functions, Microsoft 365 data, connections, webhooks, public links, MCP Apps, audit streaming and backups. Anything unfinished is marked Preview in the docs. Try it with a small group first.

Do we need wildcard DNS or a wildcard certificate?

No. Apps live at paths on one hostname, like bunker.corp.com/s/holiday-requests. One DNS record, one certificate. A separate content domain is optional for extra isolation.

Can apps be made public?

Only if an admin allows it. By default every request needs someone signed in to your Bunker. An admin can switch on public links in Admin → Sharing; then an owner can let anyone with the link view a site, like a portfolio or an event page. Public visitors see the published version only, can’t use the app’s data, and one switch closes every public link at once.

Which AI models can it use?

Your admin picks one: Anthropic Claude, OpenAI, Azure OpenAI or any OpenAI-compatible endpoint, including local models. Keys stay on the server. Each person and each site gets a daily allowance. Without a provider, everything except the AI parts still works.

What if an app author is malicious?

The sandbox stops an app from reaching your session, other apps or the internet on every modern browser. On Chromium and Edge it also blocks WebRTC and navigation leaks. The security docs list what remains, honestly.

How many people can one server handle?

Bunker is built for 500 to 5,000 people on one small VM. It is one Go binary and one SQLite database, with content-addressed files served precompressed.

What does it cost?

Nothing. Bunker is MIT licensed. You pay for the machine it runs on and, if you turn it on, your AI provider.

What happens to our apps if we stop using Bunker?

They are plain HTML, CSS and JavaScript files. Download any version and host it anywhere.

What happens to someone’s apps when they leave?

When an admin disables a person, Bunker asks who should get their sites and moves them in the same step, so nothing is orphaned. You can also archive apps nobody has opened for a while: owners get a heads-up a week before, and an editor can bring one back with one click.

Give yourself, your team or your company a safe place to build.

Free and open source. Up in minutes on a machine you control. Company sign-in whenever you want it.