A developer's bento — six compartments, one carefully packed craft.
scroll to open ▾
Each pocket holds a different facet of how we build — a principle, a feature, a recipe. Hover any compartment; it tilts toward you.
Every bento begins with rice. Every project begins with foundations. Lunchbox.dev provides the staple base: a runtime, a router, a build pipeline, and a deploy target — all chosen so that ninety percent of your day is just writing the part of the application that only you can write.
$ lunchbox init ./mochi-shop # ✓ runtime ready in 0.8s # ✓ deploy target: edge-jp1
Compartments, not containers. Each module of your stack knows its neighbors and communicates through clean, documented seams. No glue code, no adapter sludge.
The CLI — small, sharp, surprisingly satisfying. Init, dev, build, deploy. That's the verbs. The rest is flags you'll never need until the day you do.
Editor integrations that surface what you need without demanding attention. Errors with reasons, not just stack traces. Defaults from real-world usage.
90s init → first deploy
The small things that lift the whole meal: smart logs, readable diffs, dev-server proxies that just handle CORS, websockets, and auth-forwarding.
“Speed is a feature. Reliability is a requirement. Clarity is a gift.”
Open source at the core, built by a distributed team across 14 time zones. Documentation written by the community, for the community. Pull up a chair.
join the table →