Backend

Most Proyecta apps don’t need a backend you manage. Your data, sign-in, payments, email, and file storage are platform capabilities Proyecta runs for you — there’s no per-app server to deploy, scale, or pay for.

For a typical app, “the backend” is something you never have to think about. Proyecta provides it:

• Your data lives in the built-in CMS — a managed, Postgres-backed store your app reads and writes through typed hooks, with no server code to write.
• Capabilities cover the usual backend jobs: payments (Stripe), forms and submissions, sign-in, email, push notifications, file storage, and connectors to third-party APIs. Proyecta manages the credentials and the server side.
• The AI gateway lets your app call frontier LLMs without your own API keys.

Your app reaches all of it from its front-end code, over Proyecta’s managed API — the AI wires the calls for you.

What about realtime apps?

Some apps need data that changes live — a chat that updates as messages arrive, presence (“who’s online”), an activity feed, or multiplayer state. A dedicated realtime backend for these is coming soon. If you describe an app that needs live behavior today, Proyecta builds everything else and flags the live-updating piece as arriving in an update — the rest of the app ships and works now on the platform data layer.

Viewing app activity

There’s no separate backend dashboard in the builder. Ask the AI — it reads the runtime logs directly and reports errors and activity for you. Your published app runs on Proyecta’s managed infrastructure; there’s no server account of your own to log into.

Infrastructure services (local development)

For local development, your dev machine can run infrastructure services — PostgreSQL, Redis, MongoDB, MySQL — as sidecar containers alongside your app. These are development conveniences on the runtime, separate from your published app’s platform data. See Dev Machines for how they work.