Skip to main content
What runs your app, where it lives, and how it grows.

​
What is Archie Core?

Archie Core is the backend that powers every app built on Archie. It gives you: Pro includes one Starter backend, and Team includes three. Developers can also use Archie Core on its own, as a full-featured backend for apps they build themselves. See the Backend overview.

​
Does Archie handle hosting and deployment?

Yes. Your frontend is hosted on a global CDN, and your backend runs on Archie Core’s managed infrastructure. Publishing is one click, with custom domains, environments, and rollbacks. You don’t need to set up Vercel, Netlify, AWS, or any other hosting provider.

​
What database does Archie use?

A real relational database — PostgreSQL or MySQL — not a proprietary data store. Your data is portable, and you can query it with standard SQL in the SQL Playground, see its structure in a live ERD, and export it to CSV at any time.

​
Do I get APIs for my app automatically?

Yes. Every table in your data model automatically gets GraphQL and REST APIs — queries, mutations, and real-time subscriptions. You can test them in the built-in GraphQL and REST explorers, connect external clients with API keys, and send data changes to other systems with webhooks.

​
Can I generate only the backend?

Yes. Generate Backend runs independently of the frontend, straight from your plan, and builds the schema, database, and APIs. You can run it before, after, or alongside the frontend. See When to run the build.

​
Do I get separate development, staging, and production environments?

Yes, on backends that support multiple environments. Environments are isolated copies of your backend, each with its own database, roles, auth providers, and configuration. You can branch a new one from any environment, compare schemas with diff, and merge changes forward — with an automatic backup before every merge. The Starter backend includes production only; the Professional and Enterprise backends support multiple environments. See Plans and credits.

​
Which integrations are built in?

Archie Core includes built-in integrations for Stripe (payments and subscriptions), SendGrid (email), Twilio (SMS and voice), Slack (notifications), and Shopify (store data). You can add them to your plan before you build, or build your own for services Archie doesn’t ship. See Integrations.

​
Can I use my own authentication provider?

Yes. Archie includes Archie Auth, a built-in email and password system with user management, password reset, and email verification. You can also connect external providers like Auth0, Google, or AWS Cognito, or use both. See Authentication providers.

​
Can I connect a custom domain?

Yes. You can connect a custom domain to any app you build with Archie when it’s ready to go live. See Deployment.

​
What happens if I need to scale my app?

Archie Core is built to grow from first launch to production traffic without a rewrite. When you need more, upgrade a backend from Starter to Professional for dedicated compute, multiple environments, and higher quotas. Enterprise backends add dedicated, isolated infrastructure, region selection across AWS, GCP, and Azure, and SLAs up to 99.95%. See Archie Core backends.

​
Does Archie support MCP (Model Context Protocol)?

Yes. Archie supports MCP for connecting directly to ChatGPT, Claude, and other AI assistants, and apps built on Archie can support MCP too.

​
Is Archie open source?

No, Archie is a commercial platform. But what you build is yours: the code your app generates belongs to you, and so does your data. Archie builds on standard, open technologies — a React frontend and a PostgreSQL or MySQL database — so you can export your code to GitHub and your data to CSV whenever you want.

​
Does Archie support multiple languages?

Yes. You can work with Archie in the most common business languages, and you can build apps in other languages — or in several at once — for your own users.