- Dedicated Cloud: Your single-tenant instance runs in a dedicated environment that Superblocks hosts and operates on AWS.
- Managed BYOC: Your single-tenant instance runs in your AWS account.
For security reviewers: This page summarizes where each part of the platform runs, what data it stores, and what leaves your instance. To request the SOC 2 report and other security documentation, visit the Superblocks Trust Center.
Where each part runs
Each model’s page has a diagram of the full layout: Dedicated Cloud and Managed BYOC.
Platform services
The Superblocks platform is made up of these services. Each one runs inside your instance, so it’s single-tenant in both deployment models.Workload isolation
- DevBox and RunBox: Each sandbox is a single-use pod, isolated with gVisor.
- AI agents: Agents, including the Build Agent, run in microVMs on Amazon Bedrock AgentCore, in the control plane.
Control plane
The control plane is where IT and Security govern your instance. From it, they control integrations, infrastructure policies, and identity and access, and monitor everything in production.- Platform services: The Identity and Access Gateway, DevBox, the Skills Registry, CodeGuard, the control plane side of the Infrastructure Policy Engine, and Watchtower.
- Control plane server: The entry point and system of record for your instance. It manages app code, metadata, configuration, and DevBox sessions, and coordinates platform services such as the Skills Registry and CodeGuard.
- Control plane database: Stores platform data, including AI prompt and response history.
- Build Agent: Builds apps by running coding agents such as Claude Code, Codex, and OpenCode. It runs in a microVM on Amazon Bedrock AgentCore and works on the app’s code in DevBox. It sends model requests to the Superblocks Inference Gateway.
Alongside the control plane
Data planes
Data planes run your apps’ backend code and connect to your data sources. Each instance has separate non-production and production data planes, and you can add more, such as separate development, staging, and production data planes. You can also add data planes in other regions, closer to your data. See Data planes for placement and connectivity. Each data plane includes:- Platform services: The data plane side of the Infrastructure Policy Engine, RunBox, and the Integration Gateway.
- Managed database: App databases, on Amazon Aurora.
- File storage: App file storage, on Amazon S3.
How requests flow
Each flow lists the hosts it talks to, where its data is stored, and whether any of it leaves your instance. In Dedicated Cloud, your instance runs in a dedicated environment that Superblocks hosts and operates on AWS. In Managed BYOC, it runs in your AWS account.Sign-in
- A user opens your instance URL, such as
https://{tenant}.superblocks.com. - The global identity gateway at
login.superblocks.comroutes authentication to your SSO provider. It stores the user’s identity information. - The user returns to your instance with a verified identity, and the Identity and Access Gateway applies the permissions your admins assign.
Building apps
- A builder works in the editor, which runs in DevBox: a single-use, isolated sandbox in your instance that holds the app’s code and dev server.
- The Build Agent runs in its own microVM and writes and tests code in DevBox. It sends model requests to the Superblocks Inference Gateway, where inference providers don’t retain prompts or responses or train on your data.
- The Build Agent can search the web, for example for library and API documentation. In Managed BYOC, AWS Network Firewall can limit which sites it reaches.
- Package installs go to your npm registry, either public npm or your private registry, through the Superblocks npm proxy.
- To explore data schemas and sample data, the Build Agent uses tools that reach your non-production data sources through a non-production data plane. Your team decides which data it can reach. See Shared responsibility.
Deployed apps
Every request to a deployed app is checked twice: at the CDN before the app’s frontend loads, and at the data plane before its backend code runs.- When a signed-in user opens a deployed app, an edge function on the CDN checks that they’re authorized to access that app before the frontend loads.
- The app’s API calls go to the production data plane, which checks the user’s access on every request before RunBox runs the backend code.
- The Integration Gateway applies your access policies, so each user and app reaches only the business systems it’s allowed to.

