Ship before you forget why you started.
You're vibecoding. Ideas are flowing. You want to ship.
But first: config files, deployment setup, secret management, debugging infrastructure errors...
30 minutes later, the spark is gone.
jack removes the friction between your idea and a live URL.
bunx @getjack/jack new my-app # → deployed. live. done.That's it. Write code. Ship again with jack ship. Stay in flow.
Instant deployment — jack new creates AND deploys. You have a live URL before your first commit.
Works with your agent — Claude Code, Cursor, Codex, whatever. Every project includes AI context files so your agent understands the stack from prompt one.
Roaming secrets — Configure once, use across all projects. No more per-project secret ceremony.
Project tracking — 100 experiments scattered everywhere? jack ls finds them all.
No lock-in — Standard config files, standard TypeScript. Your projects work without jack installed.
# One command to create and deploy
bunx @getjack/jack new my-app
# Or install globally
bun add -g @getjack/jack
jack new my-appYou'll need Bun and a Cloudflare account (free tier works).
| Command | What it does |
|---|---|
jack new <name> |
Create and deploy a new project |
jack ship |
Deploy current project |
jack ls |
Show all your projects |
jack open |
Open project in browser |
Full documentation at docs.getjack.org
Builders who ship constantly. You spin up new projects all the time, and suddenly you have dozens scattered across your machine—each with its own env vars, secrets, and deploy setup you've already forgotten.
jack keeps you organized. One command to ship, one place to find everything, zero setup overhead. Stay creative, skip the ceremony.
In Gibson's Neuromancer, "jacking in" means plugging directly into cyberspace. The body becomes irrelevant—you're pure thought in the matrix.
jack handles the infrastructure so you stay in creative flow. The boring parts disappear. You just build.
Apache-2.0
Every deployment friction point is a creative thought lost.