Apito as a Backend (BaaS)
Apito Cloud is a managed backend-as-a-service: design models, publish schema, consume generated GraphQL (and REST where the Engine exposes it). No Docker required on Free Cloud / Pro.
Start from Console → Projects on app.apito.io.
What you get
| Capability | Where |
|---|---|
| Models & relations | Console Models, MCP, or Blueprint sync → draft → publish |
| Content UI | Auto forms/tables from published schema |
| Secured / public GraphQL | Project API keys or app-user tokens |
| Auth & RBAC | Auth · RBAC |
| Files | Files & media |
| Functions & webhooks | Functions · Webhooks |
Cloud vs Open Source
| Free Cloud / Pro / Workers | Open Source Engine | |
|---|---|---|
| Hosting | Apito-managed | You run Docker / k8s |
| Console | app.apito.io | Your console host |
| Schema publish | Console review UI | Same contract on your Engine |
| SaaS tenants | Pro (Free where offered) | Depends on your build |
Self-host when you need air-gapped or unlimited local projects — Self-hosting.
Typical flow
- Create a Free Cloud or Pro project.
- Shape schema (UI, MCP, or Blueprint).
- Publish from Schema Changes.
- Integrate with @apito-io/js-admin-sdk (or Go / Flutter / raw GraphQL).
Proof apps → public Blueprints
Production apps such as Chikly, Kisti, and Rosna inform the public packs under github.com/apito-io/examples. You do not need private monorepo access — sync from blueprints/<slug>/.