From one prompt to a 5-screen e-commerce app in Draftbit:
→ Pick the agent + model (Codex, Claude Code, …)
→ Prompt: Home, Product Detail, Cart, Checkout, Profile
→ Start from the Ecommerce template
→ Onboarding wires up a Supabase backend
→ Missing images/icons? One follow-up prompt fixes them
→ Save, then check the commit history
Full 9-min walkthrough 👇
Solo founder. No engineering team. A production-ready food delivery app.
Rajesh built ZingoEats with Draftbit. What made the difference for him:
→ API integrations handled inside the platform
→ Granular control over the design
→ Custom code + API documentation: "once I mastered those, my development speed doubled"
New Draftbit drop, as sung by our Release Cat. 🎤🐱
🔗 Connect repo: Draftbit works directly in your own GitHub repo — saving commits to the branch you choose
💾 Backups: your app's code, backed up daily when it changes (or hit "Back up now")
⏪ Publish any saved version again to Web, iOS or Android
👀 Skills: coming soon
🤖 Made with AI
A Hono API backend in Draftbit, start to finish:
→ New app → API Backend (Hono)
→ Database: managed Supabase, Cloudflare D1, or external Postgres
→ The builder reads your OpenAPI doc and turns the canvas into an API console
→ Pre-filled path, query, headers and body → Send → JSON response
→ Copy as cURL, plus request logs and generated API docs
Release notes: draftbit.com/whats-new/proje…
New in Draftbit: automatic app backups.
→ Draftbit checks your app once a day and backs it up only if the code changed, so no duplicate copies
→ Need a copy right now? "Back up now" works even mid-edit
→ Every backup is a downloadable zip of your source code, one per branch
→ Restore by importing the zip as a new app (your original stays untouched)
Your latest backup is always kept while your plan includes backups.
New in Draftbit: Connect repo.
Your GitHub repository stays the source of truth. Draftbit works right inside it:
→ Saving in the builder commits straight to the branch you choose
→ No migration, and Draftbit doesn't rewrite your project to fit its conventions
→ Monorepo? Point it at a folder like apps/mobile
→ Someone pushed to main outside Draftbit? Hit Sync and keep going
→ Connect with the Draftbit GitHub App, or a fine-grained token if you prefer
You still get chat, code edits and a live preview.
Import copies your code into Draftbit. Connect repo keeps it where it already lives.
Draftbit builds backends now, too. 🔌
Pick an API Backend (Hono), choose your database — managed Supabase, Cloudflare D1, or your own Postgres — and let the agent build it.
There's no UI to preview, so the builder swaps the canvas for an API console:
→ reads your OpenAPI doc and lists every endpoint
→ pre-fills path, query, header and body
→ sends the request with your dev key
→ Copy as cURL
→ request logs + generated API docs, right alongside
Claude Opus 5.5 and GPT-6 Sol are now live in Draftbit — the new defaults for Claude Code and Codex. 🚀
⚡ Opus 5.5: 40% cheaper to run and 30%+ faster than Opus 5 (savings vary by task)
🎯 GPT-6 Sol: about half the factual mistakes of GPT-5.6 Sol
💸 GPT-6 Luna: beats GPT-5.6 Sol for a tenth of the cost
Which one are you trying first?
File edits in Draftbit used to take 3–10 seconds.
Now they land in under 500 ms — up to 20× faster. ⚡
That's every edit: yours in the code editor and the agent's. Less waiting on your tools, more building.
Full walkthrough on YouTube: youtube.com/watch?v=w2XF5bgY…
Or start building free at draftbit.com







