The fastest way to understand Archie is to run through it once. Submit a prompt, review the blueprint Archie generates, pick your build scope and stack, and click Generate. The whole flow takes a few minutes for most projects.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.
Submit your prompt
Open archie.com (or sign in at app.archie.com) and type what you want to build into the prompt bar. One or two sentences naming the product and the users is enough — for example, “A scheduling app for hairstylists where clients book appointments by service and stylist.”If you don’t have an account, Archie creates one as part of the flow. Pick how you want to sign in (Google, Microsoft, GitHub, or email) and your prompt continues straight into blueprint generation.
Review your blueprint
Archie generates a blueprint covering everything it’ll use to build the app:
- Modules — the feature areas (e.g. Scheduling, Stylist profiles, Notifications)
- User types — the personas (e.g. Client, Stylist, Salon Admin)
- Core services — auth, file storage, real-time, search
- Integrations — Stripe, SendGrid, Twilio, and other third-party connections
- Design foundations — color, typography, layout primitives
- Technical stack — frontend framework, database, API style
Choose your build scope
Pick how much of the app you want Archie to generate:
- MVP — the core features needed to validate the idea. Faster build, lower credit cost, easy to extend later.
- Full Build — the complete app with all the features in your blueprint.
Choose your stack
Pick which layers of the app Archie should generate. Each option has its own credit cost and time estimate:
Most builders pick Full-Stack. Frontend-Only is useful when you want to wire up your own backend; Backend-Only is useful when you’re starting from an existing UI.
| Stack | What it generates | Credits | Time |
|---|---|---|---|
| Full-Stack | Frontend, backend, APIs, and database schema | ~56 | ~5 min |
| Frontend-Only | UI components, pages, client-side routing | ~18 | ~90 sec |
| Backend-Only | APIs, services, database schema, server logic | ~34 | ~3 min |
FAQ
What if my prompt isn't specific enough?
What if my prompt isn't specific enough?
The blueprint is where Archie sharpens vague ideas. If your first prompt is light, Archie still drafts a reasonable structure and you refine it from there — adding modules, renaming user types, swapping integrations. Editing the blueprint is faster and more accurate than re-prompting.
Can I change my scope after generating?
Can I change my scope after generating?
Yes. You can extend an MVP into a Full Build later, or add specific modules through the blueprint chat. Generations are additive — earlier work isn’t lost when you generate more.
What happens if generation fails partway?
What happens if generation fails partway?
Archie retries on transient failures automatically. If a generation doesn’t complete, your blueprint and any already-generated code stay intact. Open the project activity feed for the failure reason and re-run the generation. Credits are only consumed for completed work.
Why are there three stack options?
Why are there three stack options?
Some builders bring an existing frontend or backend and only need Archie to fill in the missing layer. Frontend-Only and Backend-Only are designed for those cases. If you’re building from scratch, Full-Stack is the default.
How long does Full-Stack actually take?
How long does Full-Stack actually take?
Most projects finish in 5–10 minutes. Heavier blueprints with many modules and integrations run longer. Archie shows live progress and an estimated completion time in the build view.
What’s next
Frontend
Visual editor, components, theming, and deployment.
Backend
Data model, GraphQL and REST APIs, environments, and logs.
Custom domains
Connect your domain and ship to production.
Plans and credits
Pricing, AI credits, and Archie Core backend tiers.