Available
Fully managed
Startups and new products. No infrastructure to run.
ApplicationSupero Cloud
RuntimeSupero Cloud
Datamanaged
Who operatesSupero runs every layer.
Data locationThe Supero managed database on Supero Cloud.
Platform / Deployment
Deploy each layer where you need it
Run your application, the Supero runtime and your data where your requirements say. The application runs anywhere. The runtime runs on Supero Cloud, or on your own servers. Your data stays in the managed database or in the database you already run.
Supero CloudYour cloud accountOn-premisesYour database or server
Build planeconfigures; serves no production traffic
Your AI coding agentClaude Code · Cursor · VS Code
Supero builderMCP server · App Studio
Your applicationcode in your repository
Runtimeserves your users
Applicationthe interface your agent wrote
Supero CloudAWSGCPAny Docker host
↓ HTTPS · Supero SDK
Supero runtimeAPIs, sign-in, tenancy, access, workflows
Supero CloudOn-premises
↓ stored credentials · per source
Datawhere records live
Supero managed databaseYour PostgreSQL · MySQLSnowflake · BigQuery READ
Supported configurations
Most teams start fully managed. Moving the interface to your own hosting needs no change to the application code or data models.
Available
Your app, Supero backend
Product teams with their own CI/CD and hosting.
ApplicationAWS · GCP · Docker
RuntimeSupero Cloud
Datamanaged
Who operatesYou run the interface. Supero runs the runtime and data.
Data locationSupero Cloud. Your interface calls the runtime over HTTPS.
Available
Bring your own database
Internal tools and data teams with existing systems.
Applicationanywhere
RuntimeSupero Cloud
Datayour database
Who operatesYou own the data. Supero runs the runtime.
Data locationYour database. Per table, Supero reads it live or keeps a synced copy, depending on the source.
On request
On-premises
Data-residency and regulated environments.
Applicationyour servers
Runtimeyour servers
Datayour servers
Who operatesYou run the platform. Supero supports it under an enterprise agreement.
Data locationYour data center. The AI service is not included yet, and some integrations need outbound access.
Layers and locations
Each place a layer can run, with its current status. The notes list the combinations that carry conditions.
| Layer | Supero Cloud | Your AWS account | GCP or any Docker host | On-premises |
|---|---|---|---|---|
| Applicationthe interface | Available | Available | AvailableDocker image or your own pipeline | AvailableAny server that runs your code |
| Supero runtimeAPIs, sign-in, access, workflows | Available | Runs on Supero Cloud | Runs on Supero Cloud | On request3 |
| Datawhere records live | Managed database | Your PostgreSQL1 | Your PostgreSQL1Snowflake, BigQuery: live read2 | Inside the deployment |
| Build planeMCP server, App Studio | Available | The builder runs on Supero Cloud. It handles prompts and data models, not your production records. | ||
1Your database must accept connections from Supero Cloud. The runtime connects with the credentials you store in the project, so every request crosses that link. Place the database close to Supero Cloud where you can.
2Snowflake, BigQuery and the other warehouses are read sources. Write-back works on PostgreSQL, Supabase and MySQL. Other sources sync on a schedule.
3An on-premises deployment needs outbound access for integrations, payments and Google or Okta sign-in.
4Access policies apply to traffic through Supero. Tools that connect to your database directly bypass tenant and field rules.
Check a combination
Choose where each layer runs. The result shows who runs what and lists any condition from the table above.
Application
Supero runtime
Data
Fully managed
Supero runs every layer.
ApplicationSupero Cloud
RuntimeSupero Cloud
DataSupero database
Supported configuration. No additional conditions.
What runs where
Three boundaries security reviews ask about first.
Language models
- No model runs in the request path of your application.
- MCP builds use your own model account, such as Claude, ChatGPT or Gemini.
- App Studio and the console's AI agent use platform-managed models.
Your code and data models
- An MCP build writes the application into your Git repository.
- Data models are versioned with that code as schemas.py.
- You can host the interface without Supero hosting it.
Your records
- Stored in the managed database or in your own database.
- Your application reaches them through the Supero APIs.
- Database credentials are stored per project and masked when read back.
Deployment FAQ
For a security questionnaire, see the security page or contact us.
Can I move between configurations later?
Yes, for the interface: it calls the same APIs wherever it runs, so moving it needs no code change. Moving to on-premises is planned with us.
How does the runtime connect to my database?
With the credentials you store in the project. Your database must accept connections from Supero Cloud. Each table is read live or synced on a schedule, depending on the source.
What happens if we stop using Supero?
Your application code and data models are in your repository. Data in your own database stays there, and every record in the managed database can be read out through the REST API. Applications that call Supero APIs need those services replaced.
Which configurations are available now?
Fully managed, your app with the Supero backend, and bring your own database are available now. On-premises is available on request. Release status is listed on the security page.
Plan your deployment with an engineer
Bring your security and data requirements. We will map them to a configuration.
Build, deploy and scale with Supero.
Bring a PRD and your AI. Free plan with 3 projects and preview deploys, no credit card required.