Database
Most apps store their data in Proyecta’s built-in CMS — a managed, Postgres-backed store, with no database for you to run. A realtime database for live-updating apps is coming soon.
Most Proyecta apps don’t need you to think about a database at all. When you describe your app, Proyecta designs a data model, provisions real content collections, and seeds them with sample data — all before the UI is built. Your app ships wired to real, owner-editable data from the first build. That durable data lives in Proyecta’s built-in content management system (a managed, Postgres-backed store), not in a database you have to run.
Where your app’s data lives
Section titled “Where your app’s data lives”| Kind of data | Where it lives | Manage it in |
|---|---|---|
| Content & records (posts, services, listings, FAQs, bookings) | Content management (CMS) | AI chat, your app’s admin panel |
| User accounts & sign-in | Auth | Your app’s admin panel → Members |
| Products, orders, subscriptions, payments | Commerce | Your app’s admin panel → Commerce |
| Uploaded files & media | Files & Media | Your app’s admin panel |
You never have to decide where to put content, users, orders, or files — the platform owns those, and you manage them from your app’s own built-in admin panel (or by asking the AI).
How your data is stored
Section titled “How your data is stored”You don’t design a schema or run a server. Proyecta models your data as collections and entries in the CMS, provisions them before the UI is built, and seeds them with realistic sample content. Your pages read that data through typed hooks the AI wires up, and you edit it from the admin panel — no code. For the full model (collections, singletons, field types, drafts and publishing), see Content Management and How your app’s data works.
Under the hood it’s a managed, Postgres-backed store: persistence and replication are handled for you, and there’s no database to provision, scale, or back up yourself.
Can the AI read and write data?
Section titled “Can the AI read and write data?”Yes. Ask it directly, and it works against whichever store the data lives in:
"Add a new service called 'Deep clean' priced at $120"→ creates a CMS entry"Mark the last five contact-form submissions as read"→ updates form submissions"Change the homepage headline to …"→ edits the page content
You (or anyone you make an admin) can do the same from the app’s admin panel, with no AI.
Infrastructure databases (local development)
Section titled “Infrastructure databases (local development)”If you’re developing against a traditional relational database — a repo you brought yourself, or a heavier local workload — your dev machine can run infrastructure services as sidecar containers:
- PostgreSQL — full relational database with SQL support
- MySQL — alternative relational database
- MongoDB — document database
- Redis — in-memory data store / cache
Add these by describing them to the AI, or by configuring them in proyecta.config.json. See Dev Machines for details. These are for local development and are separate from your published app’s platform data.
Where is my content stored?
In Proyecta’s built-in CMS — a managed, Postgres-backed store. Persistence and replication are handled for you; there’s no database to run. See Content Management.
Is my data backed up?
Content and records in the CMS are persisted and replicated automatically. Infrastructure databases you add for local development (PostgreSQL, etc.) are not backed up for you.
Can I export my data?
Ask the AI to export your data, or see Export Data for the available paths.
Coming soon
Section titled “Coming soon”- A realtime database — for apps that need data that changes live (chat that streams in, presence / “who’s online”, activity feeds, multiplayer game state). Durable content will still live in the CMS; the realtime store will hold only the live behavior state. If you describe an app that needs this today, Proyecta builds the rest and flags the live piece as arriving in an update.
- CSV import for bulk-loading content.