> ## Documentation Index
> Fetch the complete documentation index at: https://archie.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Archie vs. v0: which AI app builder should you use?
> Archie vs. v0 by Vercel compared: planning, UI generation, backend, hosting, editing, and when to choose each AI app builder.
**v0 and Archie both generate web applications from natural language, and they're strongest in different places.** v0, by Vercel, is known for high-quality UI and builds Next.js apps that deploy to Vercel and connect to external databases and backends. Archie is definition-first: it generates a plan of the whole app that you shape before any code is written, and every app ships with its own backend — database, APIs, auth, and environments — on Archie Core.
Last reviewed September 2026, based on v0's public documentation and pricing. Competitor products change often — if something here is out of date, tell us at [support@archie.com](mailto:support@archie.com).
## At a glance
| | Archie | v0 |
| - | - | - |
| **Starting point** | A structured [plan](/docs/features/plan/overview) of the whole app | A prompt in chat |
| **Frontend stack** | Generated React app on a global CDN | Next.js with React, Tailwind, and shadcn/ui |
| **Backend** | Included: [Archie Core](/docs/features/backend/overview) with PostgreSQL or MySQL, GraphQL and REST APIs, auth, roles | Connects to external databases and backends |
| **Environments** | Git-like [environments](/docs/features/backend/environments/overview) with branching, schema diff, merge, and backups | Vercel preview and production deployments |
| **Hosting** | Frontend on a global CDN, backend on Archie Core | Vercel |
| **Editing after build** | Chat, visual editor, draw mode, code editor | Chat and a VS Code-style editor |
| **Code sync** | Two-way GitHub sync on paid plans | Git integration |
| **Free plan** | 50 AI credits per month | \$5 in monthly credits |
## How each one works
**v0** started as a UI generator and has grown into a full-stack builder. You describe what you want, and v0 generates a Next.js app using React, Tailwind, and shadcn/ui, with a strong default visual finish. It includes a code editor, Git integration, and a sandbox runtime, connects to external databases and services, and deploys to Vercel in one click.
**Archie** starts with a [plan](/docs/features/plan/overview): overview, modules, user types, system services, and integrations, all editable. **Generate Frontend** lays out every screen in a [UI architecture](/docs/features/frontend/generating) and builds a click-through prototype with your design system applied. **Generate Backend** builds the schema and APIs on [Archie Core](/docs/features/backend/overview). **Generate Full-Stack** turns the prototype into a deployed app. See [How Archie works](/docs/introduction/getting-started/welcome#how-archie-works).
## Key differences
### Included backend vs. connected backend
v0 builds the application and connects it to the database and services you choose, which fits teams that already have a backend or a preferred provider.
With Archie, the backend is part of the product. Every app runs on [Archie Core](/docs/features/backend/overview): a relational database with a visual [data model](/docs/features/backend/data-model/overview), auto-generated [GraphQL](/docs/features/backend/graphql-api-explorer/overview) and [REST](/docs/features/backend/rest-api-explorer/overview) APIs, [Archie Auth](/docs/features/backend/app-services/authentication-providers/archie-auth/overview) or your own [auth provider](/docs/features/backend/app-services/authentication-providers/overview), [role-based access](/docs/features/backend/app-services/role-based-access), [file storage](/docs/features/backend/app-services/file-manager), and [notifications](/docs/features/backend/app-services/notifications/overview) — managed in one place, with nothing extra to wire up.
### Planning the whole app first
Archie generates a plan before code: who the users are, what each user type can do, which modules the app needs. From the plan, the [UI architecture](/docs/features/frontend/generating) maps every screen with its own spec and access level, so the build covers the whole app, not one screen at a time. See [Why the plan comes first](/docs/introduction/getting-started/welcome#why-the-plan-comes-first).
### Design system and visual editing
v0 is known for polished UI out of the box. Archie applies a full design system in the [prototype](/docs/features/frontend/prototype/overview) — [theme](/docs/features/frontend/prototype/design/theme), [color](/docs/features/frontend/prototype/design/color), [type](/docs/features/frontend/prototype/design/read), [feel](/docs/features/frontend/prototype/design/feel), and [polish](/docs/features/frontend/prototype/design/polish) — before the app is built, and after the build you can change any element with the [visual editor](/docs/features/frontend/visual-editor) or mark up the preview with [draw mode](/docs/features/frontend/draw-mode).
### Environments
Archie Core backends support Git-like [environments](/docs/features/backend/environments/overview) for your data and schema: branch, [diff](/docs/features/backend/environments/diff), [merge](/docs/features/backend/environments/merge), and restore from [backups](/docs/features/backend/environments/backups). Multiple environments are available on Professional and Enterprise backends.
## When to choose v0
* You work in Next.js and deploy on Vercel.
* You mostly need high-quality UI, landing pages, or screens for an app that already has a backend.
* You want to bring your own database and services.
## When to choose Archie
* You want the whole app — frontend and backend — generated and managed in one platform.
* You want the app defined before code: users, roles, modules, and every screen.
* You need role-based permissions, row-level filters, webhooks, and environments without assembling them yourself.
## FAQ
### Is Archie a v0 alternative?
Yes, especially if you want the backend included. Both generate web apps from natural language; Archie adds a plan-first workflow and runs every app on its own backend, Archie Core.
### Does Archie use Next.js?
Archie generates a React frontend and chooses and manages the stack for you, so you don't configure it. If you have a hard requirement, mention it in your prompt before you generate. See [What tech stack does Archie use?](/docs/faq/the-plan#what-tech-stack-does-archie-use)
### Do I need Vercel or Supabase with Archie?
No. Archie hosts your frontend on a global CDN and runs your backend on Archie Core. See [Does Archie handle hosting and deployment?](/docs/faq/infrastructure#does-archie-handle-hosting-and-deployment)
### Can I use Archie and v0 together?
Yes. Archie Core can be used on its own as a backend, with auto-generated GraphQL and REST APIs any frontend can call. See the [Backend overview](/docs/features/backend/overview).
## Related comparisons