Fabricate
Fabricate is an AI app builder that turns a single natural-language prompt into a deployed full-stack web application: React frontend, backend, database, authentication and Stripe payments, running on Cloudflare, with code you own and can export.
What is Fabricate?
Fabricate is an AI-powered platform that turns a natural-language description into a complete, production-ready web application. You describe what you want, and the system writes the code, shows it running in a live preview and deploys it. There is nothing to install and, according to every product page, no coding required. What comes out is genuinely full-stack rather than a front-end mock-up. The interface is React 18 with TypeScript, Vite, Tailwind CSS 4 and shadcn/ui components copied into the project rather than hidden behind a black box. The backend runs on Hono.js on Cloudflare Workers, and data sits in Cloudflare D1, a managed serverless SQLite database. Sign-up, login, sessions and passwords are generated from the prompt, as are Stripe checkout, subscriptions, one-off payments and billing management. Third-party APIs can be wired in by description, producing typed clients, server-side proxies, Cloudflare secrets, signature-verified webhooks, retries and rate limiting. One distinction matters here: Fabricate itself exposes no public API; what it offers is the ability to build applications that expose and consume them. The workspace is a browser IDE with a sandboxed live preview, a file explorer, a code view and a version history you can restore from in one click. Two modes share it. Build Mode writes code and spends credits, one credit being 10,000 weighted tokens of input and output, with a first app typically costing three to eight. Discuss Mode is free and unlimited, meant for planning and advice before any credit is spent. Arbitrary npm libraries can be added simply by asking for them. Deployment is one click to the Cloudflare edge with automatic SSL. Custom domains and password-protected private projects come with the paid tiers, while free-plan projects stay public. You own what is produced, and paid plans allow a ZIP download, a GitHub push or two-way sync so the project can continue in a local git workflow. The site groups roughly 35 features into AI building, infrastructure, stack and frameworks, and deployment and integration, and showcases ten app archetypes from a subscription dashboard to a booking system. Its stated limits are equally clear: the stack is fixed, native iOS and Android are not supported, and native hosting is Cloudflare only.
What it does
- Turn a plain-language description into a complete, working full-stack web application
- Generate a database, user authentication and Stripe payments in the same pass as the interface
- Iterate by conversation: change a feature, fix a bug, add a screen, with each change redeployed
- Publish to a live URL in one click on the Cloudflare edge, with SSL handled automatically
- Export the code as a ZIP, push it to GitHub or keep a two-way sync (paid plans)
- Restore any earlier version of a project in one click from the version history
- Plan a build and ask for advice in Discuss Mode without spending a single credit
When to use Fabricate / When not to
A quick filter to help you decide if Fabricate is the right fit.
When to use Fabricate
- Founders and indie hackers who need an MVP or prototype live in hours rather than weeks
- Freelancers and small agencies delivering client apps within a predictable monthly credit budget
- Business teams building internal tools without waiting in the IT department's queue
- Non-developers who want a working product without writing code, since no coding is required at any step
- Developers who want a fast first draft they can export by ZIP or GitHub sync and keep building locally
When not to use Fabricate
- Teams that need native iOS or Android applications, since only progressive web apps and responsive web apps are produced
- Engineering teams that must choose their own stack, because the generated stack is fixed and currently not configurable
- Organisations that require a signed DPA, a SOC 2 or ISO 27001 certification, or a contractual sub-processor list, none of which is published
- Companies bound to a hosting provider other than Cloudflare, at least without exporting the code and redeploying it themselves
- Users located in the 48 countries and territories where account access is unavailable, and anyone under 13 years old
How to use Fabricate
A typical end-to-end flow, from setup to results.
- Sign in through a third-party provider such as Google or GitHub, handled by Clerk; no payment card is needed to start
- Open Discuss Mode first if you want to plan the application and ask questions without spending credits
- Write a prompt describing the app you want, attaching screenshots, wireframes or reference designs if they help
- Follow the documented prompting advice: be specific, describe the outcome, and build one feature at a time
- Watch the AI generate the React and TypeScript code, with the live preview updating as it builds
- Iterate in conversation to adjust a feature, fix an issue or add a screen, with every change redeployed
- Ask for extra npm libraries or third-party API integrations directly in the prompt when you need them
- Restore an earlier version in one click if a change goes the wrong way
- Use the Publish assistant to choose a subdomain and visibility, then deploy to a live URL in one click
- On Pro or Scale, attach a custom domain and export the code by ZIP download, GitHub push or two-way sync
Pros & Cons
Pros
- Genuinely full-stack output with database, authentication and payments, where several competitors stop at the interface
- Code you own and can take away, via ZIP export, GitHub push and two-way sync, with no claimed vendor lock-in
- The same AI model on every plan, with the publisher stating there is no tier-gating on AI quality
- A permanent free plan of 60 credits per month with no payment card required, plus a Discuss Mode that costs nothing at all
- Credits are not charged for the AI's own mistakes, and any earlier version can be restored in one click
- Unusually explicit data commitments: no training on prompts or generated content, and thirteen sub-processors named with role and location
- Public, itemised pricing with a credit grid and consumption examples, annual billing at 20% off, and a page naming the countries where access is restricted
Cons
- No public API for Fabricate itself: the only OpenAPI spec referenced in the docs is Mintlify's sample template, and the API reference page returns a 404
- The generated stack is fixed and currently not configurable, and native deployment is limited to Cloudflare
- No native mobile application, neither for the tool nor as generated output, only progressive and responsive web apps
- Credits cannot be bought individually, never roll over on any plan, and are lost immediately if the publisher terminates an account for breach of the terms
- No DPA, no named Article 27 EU representative, no security certification such as SOC 2 or ISO 27001, and no published postal address behind the sole mention of Fabricate, LLC
- The free plan's daily credit cap is published inconsistently: 45 credits per UTC day on the pricing page against 15 credits per day in the documentation, both online on the same day
- A very young product with no verifiable usage figures, since the homepage counters are empty in the served HTML, and support is by email only with priority support reserved for Scale
Pricing & Plans
A permanent free plan is available at 0 USD, offering 60 credits per month, one published project, public projects only, the web IDE and preview, one-click deployment and community support, with no payment card required to start. The lowest paid entry point is the Pro plan at 25.00 USD per month, or 240 USD billed annually, which represents a 20% discount presented as two months free; the Scale plan is 50 USD per month or 480 USD per year. Consumption is metered in credits, one credit corresponding to 10,000 weighted tokens of input and output. The publisher documents typical costs of 3 to 8 credits for a first app, 1 to 3 for a small interface change, 3 to 10 for a new feature, 8 to 20 for a major rework and 10 to 25 for a complex multi-file change, and states that most paying apps ship in 5 to 15 credits on Pro. Credits reset at each billing cycle without roll-over, additional credits cannot currently be purchased, taxes are added, and refunds are discretionary and excluded once more than 10% of credits have been consumed. One inconsistency deserves attention before budgeting: the free plan's daily credit cap is published as 45 credits per UTC day on the pricing page and as 15 credits per day in the documentation.
- 60 credits per month
- a daily credit cap (45 per day according to the pricing page
- 15 per day according to the documentation)
- one published app
- public apps only
- web IDE and preview
- one-click deployment
- GitHub sync and community support
- 350 credits per month
- unlimited published apps
- no daily cap
- custom domains
- password-protected private apps
- code download and export
- GitHub push and two-way sync
- unlimited project sharing
- 700 credits per month
- unlimited published apps
- everything in Pro plus dedicated priority support
- All three plans use the same AI model quality and include unlimited Discuss Mode
- No enterprise tier is published
- higher-volume and enterprise needs are handled by contacting the team at sales@fabricate.build
Data, GDPR & hosting
A consolidated view of how Fabricate handles your data.
GDPR overview
The privacy policy, effective 6 March 2026, carries a dedicated GDPR section for the EEA, the United Kingdom and Switzerland, and a separate CCPA/CPRA section for California. Legal bases are stated one by one: contract performance, legitimate interests, legal obligation, and consent for analytics cookies, marketing pixels and session recording. Rights are listed in full: access, rectification, erasure, restriction, portability, objection, withdrawal of consent and complaint to a supervisory authority, the ICO being named for the UK. Requests go to support@fabricate.build, with a 30-day response target extendable by 60 days (45 days, extendable to 90, for CCPA). Transfers rely on the European Commission's standard contractual clauses, UK IDTAs and the EU-U.S. Data Privacy Framework. Three gaps remain: no Article 27 EU representative is named although the policy alludes to one, no data protection officer is designated, and no DPA is published or offered.
Who owns the data?
The terms state that you keep ownership of what you submit, meaning your prompts and the applications generated from them. You grant Fabricate, LLC a limited, worldwide, royalty-free licence to process, store and transmit that content solely to run the service, keep it secure and answer support requests. Ownership of the generated code also stays with you: the publisher explicitly claims no ownership over the output, subject to applicable AI provider policies. The platform's own design, software, trademarks and documentation remain the property of the publisher or its licensors. Feedback and suggestions may be used without restriction or compensation. Card details are handled by Stripe, not stored by the publisher.
Reuse rights
Because you own the applications and code produced by the service, you can reuse, modify, publish and commercialise them without asking permission, subject to the applicable AI provider policies. On Pro and Scale, the code can be downloaded as a ZIP, pushed to GitHub or kept in two-way sync so a project can continue in a local git workflow. On its own side, the publisher lists the purposes for which it processes personal data: creating and authenticating accounts, delivering and improving the service, processing payments and subscriptions, metering credit consumption and enforcing plan limits, sending transactional and lifecycle emails (with an unsubscribe option), detecting and preventing fraud, incidents and abuse, complying with legal obligations, and analysing aggregated usage trends. Two commitments are explicit: prompts and generated content are not used to train AI models, and personal data is not sold to third parties for advertising. Data is shared only with the thirteen named sub-processors, among them Stripe, Clerk, Cloudflare, Anthropic, Resend, PostHog, Sentry, Crisp and GitHub, and where the law requires it. The categories collected cover account data (name, email, profile picture from the identity provider), billing data, prompts and generated content, support conversations, the GitHub account if sync is enabled, plus automatically collected usage, log and device data.
Data retention & training
Hosting summary
Fabricate, LLC is based in the United States, and the privacy policy states plainly that personal data from users in the EEA, the UK or Switzerland is transferred to and processed in the USA and in other countries whose data protection laws may not be equivalent. Transfers rely on the European Commission's standard contractual clauses, UK IDTAs and the EU-U.S. Data Privacy Framework for certified vendors. The infrastructure layer, covering CDN, serverless compute, database and storage, is Cloudflare, whose declared location is global; generated apps run on Cloudflare Workers with D1 and answer from the data centre closest to the visitor. The other named sub-processors are almost all US-based, including Stripe, Clerk, Anthropic, Resend, Sentry, Meta, Google, Reddit, Tolt and GitHub, with PostHog in the US and the EU and Crisp in the EU. Disclosed security measures are encryption in transit over TLS, access controls and security monitoring, with notification in the event of a breach. What is not offered: no customer-selectable hosting region and no guaranteed data residency, so an organisation with a strict residency requirement will not find a control for it here.
Where Fabricate works
Country-level availability.
Not available in
Things to keep in mind
Risks and trade-offs to weigh before adopting Fabricate.
- The free plan's daily credit cap is contradictory, at 45 credits per UTC day on the pricing page against 15 credits per day in the documentation, so budget on the lower figure until the publisher clarifies
- Credits do not roll over and cannot be bought individually: running out mid-build blocks the work until the next cycle or forces an upgrade, and any remaining credits are lost without refund if the publisher terminates the account for breach of the terms
- Refunds are at the publisher's sole discretion and excluded beyond 10% of credits consumed, paid subscriptions renew automatically, and a chargeback triggers immediate account suspension
- The publisher's legal footprint is thin: no postal address, no named Article 27 EU representative although the privacy policy alludes to one, no DPA and no claimed security certification, with an AAA arbitration clause, a class-action waiver and Delaware law governing disputes
- Account access is unavailable in 48 countries and territories, several of them large markets such as India, Indonesia, Nigeria, Pakistan, the Philippines, Vietnam, Bangladesh and Egypt, with regional pricing announced only as work in progress
- One account per person is allowed, and creating multiple accounts leads to the suspension of every linked account
- The real cognitive risk is shipping software you have not read: an app you cannot debug, review or secure yourself becomes a dependency that only reveals itself when something breaks, and it rests on a fixed stack, a single named AI sub-processor (Anthropic) and a product with no verifiable track record before March 2026
Setup & Integrations
Technical difficulty
Very low. Nothing to install: everything happens in the browser, which must support JavaScript and HTML5. An account is opened through a third-party provider such as Google or GitHub, handled by Clerk, with no payment card. The quickstart documents a first app built and deployed in under five minutes, and every product page repeats that no coding is required. The only real prerequisite is writing a precise request, and the publisher provides prompting guidelines and examples. More technical, optional steps: connecting a custom domain through DNS records, linking GitHub, and storing API keys as environment variables.
Deployment
Integrations
Supported languages
Behind Fabricate
Resources
All the official URLs gathered for verification and reference.
Alternatives
Tools that compete with or complement Fabricate.
Frequently asked questions
Does Fabricate build real applications or just mock-ups?
Can the apps I build take payments?
Can I export the code?
What happens if the AI breaks something?
What exactly is a credit?
Can I buy extra credits when I run out?
Are my projects private?
Can I build a native mobile app?
Are my prompts used to train AI models?
Can I change the technical stack?
Should you pick Fabricate?
Fabricate delivers on the scope it claims. The output is genuinely full-stack, with a database, authentication and Stripe payments generated alongside the interface; the code is exportable and owned by the user on paid plans; and the pricing is public, itemised and explained down to the credit. For a founder validating an idea, a freelancer shipping client work or a business team building an internal tool without an IT queue, that combination is hard to fault at 25 USD a month, with a permanent free tier and an unlimited Discuss Mode to plan before spending anything. Two things stand out as unusually transparent for a product this young: the explicit commitment not to train models on prompts or generated content, and a privacy policy that names thirteen sub-processors with their role and location. The public page listing the countries where account access is restricted belongs in the same column. The enterprise layer, however, is simply not there yet. No DPA, no SOC 2 or ISO 27001, no named Article 27 EU representative, no postal address behind Fabricate, LLC. Procurement at a regulated company will stop on those points. The stack and the hosting are fixed choices, React on Cloudflare, so flexibility is what you trade away, and the code can only move once you export it. The product is also very new, its first public trace dating from March 2026, with no verifiable usage figures. Two things to check before committing. First, the free plan's daily credit cap is published as 45 credits per day on the pricing page and 15 in the documentation, so ask which figure applies before planning around it. Second, credits never roll over and cannot be topped up individually, so choose the tier that matches a realistic month rather than a best case.
- Choosing a selection results in a full page refresh.
- Opens in a new window.