Draftbit
Draftbit is a browser-based builder that turns plain-English prompts into real React Native, Vite and Astro projects. Claude Code and OpenAI Codex edit the same files as its visual editor, and every line of code stays yours to export.
What is Draftbit?
Draftbit is a browser-based application builder for native mobile apps, web apps and websites. It presents itself as a low-code platform where three ways of working act on the same project: prompting an AI agent, editing on a visual canvas, and writing code directly. Every path edits the same files, so nothing has to be rebuilt when you switch between them.
The generated projects are ordinary TypeScript codebases. Mobile apps are React Native on Expo, web apps use Vite, websites use Astro, API backends use Hono, and CMS projects use Payload. Two coding agents run inside the project sandbox: Claude Code from Anthropic and Codex from OpenAI, with models from Google, xAI, DeepSeek and Meta reachable through OpenRouter. Agents read files, run checks, install packages, call connected APIs and stop to ask when a decision is needed. You can pay for them with Draftbit credits or plug in your own OpenAI, Anthropic or OpenRouter key, even on the free plan.
The visual editor is a live view of that source. It exposes the component tree, a styles panel with Tailwind classes, drag-and-drop, design blocks, a theme editor, Google Fonts and responsive breakpoints. Each project gets a dedicated cloud sandbox with dependencies installed, a running dev server, and separate development, staging and production environments. Previewing spans the browser, 26+ device simulators, a before-and-after comparison and a QR-code launcher for real devices.
Data comes from a Supabase backend that Draftbit can provision in open beta, from Firebase or Xano, or from any REST or GraphQL endpoint: 45 REST integrations and 15 MCP servers ship preconfigured, and custom sources can be added. Publishing sends web builds to a draftbit.dev address or your own domain, and native builds to App Store Connect and Google Play under your own developer accounts.
Draftbit also sells the human half: an in-house team of designers, developers and backend engineers available as fixed-price packages, monthly retainers or weekly advisory. The site claims a 4.8 average rating, more than 200,000 builders and over 50,000 apps created.
What it does
- Generate a working mobile, web or website project from a plain-English description
- Run Claude Code or OpenAI Codex agents that read and edit the real project files
- Adjust layout, styles, typography and content visually on an infinite canvas
- Connect a backend: a provisioned Supabase database, Firebase, Xano, or any REST or GraphQL API
- Preview the app on 26+ device simulators and on a real phone through a QR code
- Publish to the web, the App Store and Google Play from a single workflow
- Export the full TypeScript source as a ZIP or push it to a GitHub repository
When to use Draftbit / When not to
A quick filter to help you decide if Draftbit is the right fit.
When to use Draftbit
- Non-technical founders who want to ship a real iOS and Android app without hiring an engineering team
- React Native and Expo developers who want AI agents and a visual editor on top of an ordinary TypeScript codebase
- Product managers and designers who need a shareable prototype that can become the published app in the same project
- Freelancers and small agencies delivering client apps, who need editor roles, ZIP exports and GitHub hand-off
- Teams building internal tools, admin dashboards or e-commerce and booking apps from a ready-made template
When not to use Draftbit
- Anyone who needs a desktop application for macOS, Windows or Linux, which Draftbit explicitly does not target
- Backend teams committed to Python, PHP or C#, since projects are generated in TypeScript with Hono or Supabase
- Studios building graphics-heavy games, a use case the FAQ rules out
- Organisations that require every tool to run inside their own network, as builds happen in a cloud sandbox
- Buyers with strict procurement requirements, because no DPA, subprocessor list or security certification is published
How to use Draftbit
A typical end-to-end flow, from setup to results.
- Create a free account from the "Get started free" button; no payment details are required
- Describe the app you want, or open one of the mobile, web or website templates
- Let Draftbit build a first working version before you even open the editor
- Iterate in chat threads, keeping each thread scoped to one feature or task
- Refine visually: select an element in the preview or the component tree and edit its styles, text or code
- Connect your data on the Integrations page through REST, GraphQL, MCP or a provisioned Supabase backend
- Test the result on the browser preview, on device simulators, or on a real phone with the Draftbit Preview app
- Publish to the web first, then to iOS and Android under your own Apple and Google developer accounts
- Ship updates by publishing again with a new version name and number
- Take the code with you whenever you want: ZIP export from Standard, GitHub push from Pro
Pros & Cons
Pros
- Produces real, exportable React Native, Expo, Vite and Astro code instead of a proprietary format
- Code ownership is stated plainly, and Draftbit says it does not train AI models on customer code
- Prompting, visual editing and hand-written code all act on the same files, without switching tools
- Your own OpenAI, Anthropic or OpenRouter key can replace Draftbit credits, from the free plan upwards
- The free plan has no time limit and includes the agents, the visual editor and web publishing
- Publishing runs end to end: build, signing and upload to App Store Connect and Google Play
- An in-house expert team can take over integrations, rescues or store submissions when AI stalls
Cons
- The technical stack is imposed: no Python, PHP or C# backend, no desktop app, no graphics-heavy game
- Saving your own code edits requires the Standard plan, and GitHub export requires Pro
- Only one editor seat is included on Free, Standard and Pro; extra seats cost 8 to 16 USD per month
- No DPA, no subprocessor list and no security certification such as SOC 2 or ISO 27001 is published
- No hosting country or region is named anywhere in the privacy policy
- Credits expire: thirty days for monthly credits, one year for one-off purchases, and subscriptions are non-refundable
- Importing an existing app is limited to Expo projects hosted in a public GitHub repository
Pricing & Plans
Draftbit offers a permanent free plan with no time limit, which includes the AI agents, the visual editor, a one-time grant of 5,000 credits and web publishing on a draftbit.dev address. The lowest paid entry point is the Standard plan at 12.00 USD per month when billed annually, or 15.00 USD per month on monthly billing. Draftbit credits are optional, since threads running on your own AI key or subscription consume none; when purchased, credit packages start at 25.00 USD per month and one-off top-ups run from 5.00 USD to 10,000.00 USD at 1,000 credits per dollar. Payment is by Visa, Mastercard or American Express through Stripe, in US dollars.
- Claude Code and OpenAI Codex
- mobile
- web and website projects
- all visual editing features
- built-in Supabase backend
- your own AI key or subscription
- 5
- 000 one-time credits
- unlimited projects
- unlimited REST integrations
- full agent and model choice with credits
- full code editing and export
- one-click iOS
- Android and web publishing
- custom domains
- Draftbit branding removed
- up to 5 concurrent agents
- custom MCP servers
- GitHub export
- larger and faster sandboxes (up to 3)
- iOS and Android simulators
- App Store submission assistance
- priority support and training
- extra seats at 16 USD per seat per month
- 10 editor seats included
- live collaboration
- up to 10 concurrent agents
- up to 5 sandboxes
- team training sessions
- dedicated account manager
- custom onboarding
- early access to new features
- custom credit allocations
- unlimited seats
- unlimited concurrent agents and sandboxes
- SSO and SAML
- custom SLAs
- dedicated infrastructure
- private or self-hosting options
- custom integrations
- Starter Backend from 2
- 500 USD
- MVP from 6
- 499 USD
- v1 from 12
- 999 USD
- advisory from 150 USD per week or 500 USD per month
- monthly development plans from 2
Data, GDPR & hosting
A consolidated view of how Draftbit handles your data.
GDPR overview
The privacy policy names the GDPR explicitly, alongside PIPEDA, Quebec Law 25, LGPD, CCPA/CPRA, POPIA, the Swiss FADP and around fifteen US state statutes. Data subject rights are listed article by article: access (15), rectification (16), erasure (17), restriction (18), portability (20), objection (21) and complaint (77), with a link to the EDPB list of supervisory authorities. Transfers outside the EEA rely on EU standard contractual clauses or equivalent measures, with a link to decision CELEX 32021D0914. Requests go through a form on the privacy page or to help@draftbit.com, addressed to a "Data Privacy Officer of Draftbit" who is not named. No Article 27 EU representative is designated, and no data processing agreement is offered.
Who owns the data?
The applications you build, their source code and the assets you bring belong to you, and Draftbit states it claims no ownership over what you create. Your app data lives in whichever backend you connect; a Supabase project provisioned by Draftbit can be moved into your own Supabase organisation, and a backend you already run stays governed by your agreement with that provider. Draftbit does keep ownership of its own website and platform content under the intellectual property clause of its Terms of Service. Prompts you send are stored with the chat thread, and when they travel on your own AI key they fall under that provider's terms.
Reuse rights
You may reuse everything you create without asking permission. Code written by the agents, by you or by Draftbit's own experts is yours: you can edit it, download it as a ZIP from the Standard plan, push it to a GitHub repository from the Pro plan, and keep building it outside Draftbit with standard React Native, Expo, Vite, Astro, Hono or Payload tooling. Draftbit states that it does not use your code to train AI models. The opposite direction is restricted: the Terms of Service forbid reproducing, redistributing or republishing Draftbit's own website material, and downloadable applications are governed by a separate EULA.
Data retention & training
Hosting summary
Draftbit names no hosting country and no hosting region. The privacy policy states only that, where possible, data is stored and processed on servers within the general geographical region where the user resides, adding that this may not be the country of residence. Personal data may also be transferred to and held on servers outside the user's state, province or country. Data may be kept in countries considered adequate; for regions that are not, Draftbit says it enters into EU standard contractual clauses or equivalent measures with parties outside the EEA, and links to decision CELEX 32021D0914. Each project runs in its own cloud sandbox whose location is not disclosed. Stored credentials are encrypted at rest with AES-256 and traffic uses TLS. The draftbit.com domain is served through Cloudflare, so the resolved IP address indicates a CDN edge node and says nothing about where data actually lives.
Things to keep in mind
Risks and trade-offs to weigh before adopting Draftbit.
- Prices shown by default on the pricing page are the annual rates; monthly billing costs about 25 percent more, so read the toggle before comparing
- An app that mostly works is not an app that is safe to launch: authentication, payments and data access still need a technical review, as Draftbit itself warns
- Leaning on the agents can hollow out your understanding of your own product, and the site openly sells a rescue service for stuck AI-generated apps
- Downgrading locks code export and mobile publishing, so retrieve your source before the paid period ends
- Threads running on your own AI key are governed by that provider's retention and training terms, not by Draftbit's
- No DPA, no subprocessor list, no named hosting country and no Article 27 representative: a real obstacle for anyone processing EU personal data
- Apple and Google developer accounts, their fees and their identity checks remain yours, and store rejections come back to you, not to Draftbit
Setup & Integrations
Technical difficulty
Low to start, moderate to launch. No coding experience is required and nothing is installed locally: everything runs in a cloud sandbox, and a first version is generated from your description before you open the editor. Web publishing on a draftbit.dev address is immediate. Difficulty rises at release: mobile publishing needs your own Apple and Google developer accounts with possible identity checks, a custom domain needs CNAME and TXT records at your registrar, and authentication, payments and data access should be reviewed by someone technical before going live.
Deployment
Apps stores
Integrations
Supported languages
Behind Draftbit
Fundraising
Social
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement Draftbit.
Frequently asked questions
What exactly does Draftbit build?
Do I own the code, and is it used to train AI models?
Can I leave Draftbit and keep developing elsewhere?
Which AI agents and models are available?
How much does it cost to start?
Can Draftbit publish to the App Store and Google Play?
What backends and integrations can I connect?
Is there an age requirement?
How is my data protected?
What happens if I cancel or downgrade?
Should you pick Draftbit?
Draftbit occupies a clear position among AI app builders: it aims at native mobile first, and it hands back a codebase rather than a locked runtime. Prompting, visual editing and hand-written code all act on the same React Native, Vite or Astro files, and the promise of no lock-in is backed by ZIP downloads and GitHub pushes rather than left as a slogan. Ownership of the code and the absence of model training on customer projects are both stated plainly and repeatedly.
The offer is unusually complete for the price. A permanent free plan carries the agents, the visual editor and web publishing; the first paid tier starts at 12 USD per month billed yearly, and using your own OpenAI, Anthropic or OpenRouter account removes the credit meter entirely. Publishing runs all the way to App Store Connect and Google Play, and an in-house team of designers and engineers can be hired when the last twenty percent gets hard.
The limits are equally clear. The stack is imposed, desktop apps and graphics-heavy games are excluded, importing an existing project only works for Expo repositories, and a single editor seat is included right up to the Pro plan. The weakest area is enterprise compliance: the privacy policy claims GDPR alignment, yet no data processing agreement, no subprocessor list, no Article 27 EU representative and no security certification are published, and no hosting country is named.
For a founder, a designer or a developer who wants to ship a real mobile app quickly and keep the source, Draftbit is a serious and honest option. For a regulated buyer with a procurement checklist, the paperwork will have to be requested before signing.
- Choosing a selection results in a full page refresh.
- Opens in a new window.