How does Makedraft turn a chat into a deployed app?

Updated

Makedraft turns a chat into a deployed app by treating every conversation as a branch in a real GitHub repository. Your first message opens that branch, each commit the agent pushes deploys automatically as its own live service, and you can point a custom domain at the result. There is no sandbox or export step — the code is real from the start. This suits people building internal tools or customer-facing apps on React and Next.js who already work with GitHub and want deployment to happen without a separate release process.

The workflow, step by step

  1. Start a chat. According to Makedraft, the first message already opens a real branch in a real GitHub repo. There is no throwaway preview environment to discard later.
  2. Build through the conversation. The agent writes code to that branch as you describe what you want. Because the branch is a normal part of your repo, the work is inspectable and versioned like any other development branch.
  3. Commit and deploy. Each branch ships as its own live service. When the agent pushes a commit, the service redeploys automatically — you do not trigger a separate deploy step.
  4. Attach a domain. You can point a custom domain at what you built instead of staying on a shared subdomain.

The expected result at the end is a running app backed by a GitHub branch you control, reachable on your own domain if you choose one.

Why the "no export step" design matters

Most chat-based builders generate code in a sandbox and then ask you to export or migrate it before it becomes a real project. Makedraft's stated difference is that there is nothing to migrate: the repo was yours from message one. One user quoted on the site, an indie hacker, puts it as no longer worrying about "the day I'd have to migrate off it — there's nothing to migrate."

A second practical effect is deployment reliability. A freelance designer quoted on the site notes that every approved commit is live a minute later, with "no separate deploy step to forget about before a client demo." That is the mechanism to check against your own needs: if your workflow depends on a manual release gate, automatic redeploy on every commit changes how you sequence work.

What it runs on

Makedraft says it works with React and Next.js projects and runs on tools you already trust: GitHub, Render, Supabase, and Stripe. In practice that means the repo lives in GitHub, the live service is hosted on Render, and Supabase and Stripe are available for data and payments. If your team already uses these, the stack will look familiar; if you depend on different infrastructure, confirm compatibility before committing.

Choosing a model and a plan

Pro and Business plans are not locked to a single model — you can pick the model that fits the work. One early-stage founder quoted on the site describes switching models on a chat that was stuck rather than starting over. The site links to a pricing page, but the supplied material does not include prices, so check that page directly for current cost and plan limits.

When this approach fits — and when it may not

Your situation Makedraft's fit
You want code in your own GitHub repo from the first message Strong — every chat is a real branch
You want commits to go live without a manual deploy Strong — each commit redeploys automatically
You build React or Next.js apps Strong — stated support
You need a custom domain Supported — point one at what you build
You want to try multiple AI models Available on Pro and Business plans
You need a manual release gate before production Weigh it — automatic redeploy on commit may not match your process
You rely on infrastructure other than GitHub, Render, Supabase, Stripe Verify compatibility first

Getting started

You can begin from a template — the site lists categories including apps and games, landing pages, components, and dashboards, with examples such as an image generation playground and a SaaS landing page — or start a chat directly. Either way, the first message opens the repo branch, and from there the loop is: describe, commit, deploy, repeat.