Skip to main content
What you can build with Archie, and how you work with it once it’s built.

​
What can I build with Archie?

Full-stack web applications: SaaS products, marketplaces, internal tools, dashboards, CRMs, client portals, and more. Every app runs on real infrastructure — a relational database, auto-generated APIs, authentication, and production hosting. Archie is built for software you ship, not demos you throw away.

​
Can I build a SaaS product with Archie?

Yes — it’s one of the most common things people build. A SaaS needs user accounts, roles, billing, email, and a backend that grows with you, and Archie covers each of them: Archie Auth for sign-in, role-based access for permissions, Stripe for payments and subscriptions, SendGrid for email, and environments so you can test changes before they reach your customers.

​
Can I build a marketplace with Archie?

Yes. Marketplaces are hard because they have more than one kind of user, and each sees and does different things. Archie defines those user types in the plan before any code exists, so buyers, sellers, and admins are part of the design from the start. The backend handles the rest: per-role permissions with row-level filters, payments, notifications, and file storage for listings.

​
Can I build internal tools and dashboards with Archie?

Yes, and they’re a strong fit. Internal tools need a real database, sign-in, and strict permissions — exactly what Archie Core provides by default. Admin panels, CRMs, inventory systems, and reporting tools all benefit from role-based access, SQL views for reporting, and bulk data import from CSV.

​
Can I build a mobile app with Archie?

Archie generates responsive web applications that work on phones, tablets, and desktops. You can check every screen at different device sizes in the prototype. Native iOS and Android apps are not available yet.

​
Can I use images or design references when prompting?

Yes. You can attach screenshots, mockups, and other reference material when you generate your plan, and Archie uses them to inform the structure and visual direction. See Generating a plan. You can also upload your own logo and brand assets in the prototype’s branding settings.

​
How do I edit my app after it’s built?

Four ways, and you can mix them:
  • Talk to Archie — describe a change in plain language, like “add a search field to the orders page,” and Archie applies it across the right files.
  • Visual editor — click any element in the live preview and change its text, color, spacing, or position directly.
  • Draw mode — mark up the live preview and send your marks to chat for precise visual changes.
  • Code editor — edit the code in the built-in IDE, or sync with GitHub and work locally.
For structural changes — a new module, a new user type — go back to the plan and generate again.

​
Can I revert to an earlier version of my app?

Yes. The Team plan includes app versioning, so you can roll back to an earlier version of your project. On any paid plan, you can connect GitHub, which keeps a full commit history of your code. On the backend, environment backups are taken automatically before every merge and can be restored. See Plans and credits for what each plan includes.

​
Can I collaborate with my team on Archie?

Yes. Every plan includes unlimited viewers. On Pro, you can invite builders who have their own Pro subscription. On Team, you get full collaboration in a shared organization: pooled credits, role assignment, per-member credit limits, real-time collaboration, and an activity feed. Teammates can also leave comments pinned to exact spots on a screen and track them to resolved.

​
What happens when a vibe-coded app can’t scale (the “70% problem”)?

Many AI app builders get you to a working prototype fast, then stall around 70% of the way to a real product. The reason is usually the same: nothing underneath defines how the app should work, so every new feature fights the last one. Archie starts from the definition. The plan sets the modules, user types, and services before any code exists, and the backend is built on a real relational database with a proper data model, permissions, and environments. Your app has a foundation to grow on, so the last 30% is building features — not rebuilding the app.