The bet
A small website can turn into a framework project before you've written the first page. Shibumi starts with server routes, HTML, and a database when you need one.
The generated files include instructions for coding agents: where routes live, which checks to run, and which security rules to preserve. You and your agent work on the same source.
Two tools handle creation and deployment.
Create
One command, a whole app.
create-shibumi writes you a complete Bun app from a short list of curated parts, one library per job: Hono for routes, Alpine for browser behavior, Nanostores when state crosses components, Zod for validation, SQLite and Drizzle when you need data.
Three starting points: full-stack app, blog, static site. Each one gives you source you own, a deploy script, and an agents.md with the house rules. Full-stack includes app tests and container files. Blog and static generate their container files during bun ship:setup.
Got a site already? Run bun create shibumi . in it. The CLI detects your build directory and adds the deploy script and container files. Your application source stays in place.
Extensions
Features as source, in your repo.
In a full-stack project, run bun shi add auth to copy the implementation, migrations, tests, and agents/auth.md into your repo. The installer adds the dependencies the feature needs. Email, uploads, and an admin panel install the same way, each with its own agent instructions. Auth and uploads add APIs; you build the login and upload screens your app needs. Extensions docs.
Ship
A server you own.
shibumi-server runs registered apps in rootless Podman on your Linux VPS or homelab. bun ship builds committed code with Docker on your computer and uploads the image over SSH. The server verifies it against the pushed commit, starts it behind Caddy, and restores the previous image if startup or health checks fail. The default rollback window is 12 hours. Recovery can interrupt requests, and image rollback does not undo database changes. Server costs depend on the provider and the apps you run.
From your project root, run bun ship:setup. It detects the Compose service and health path and registers the app over SSH, rather than asking you to match those settings by hand.
On the side
Forms, for any static site.
Shibumi Forms is its own thing, and it works on any static site, whoever built it. Point a plain HTML form at one URL and the submissions start arriving, no client JavaScript involved. You read them in the browser and export CSV. The hosted pre-alpha is running now, and the Bun, Hono, and SQLite source is there if you'd rather run it yourself.
Try it
Give it a shot: , star it on GitHub, or get release updates.