Skip to main content
Every Superblocks instance is single-tenant, in both deployment models, and runs the same platform architecture. A small set of services runs centrally in Superblocks Cloud and serves every instance. Superblocks owns and operates these services, and each one has a specific, limited interaction with your instance.

Global identity gateway

Sign-in for every Superblocks instance goes through the global identity gateway at login.superblocks.com, which Superblocks runs on Auth0 in both deployment models. When a user signs in, the gateway routes authentication to your SSO provider, then returns the user to your instance with a verified identity. The gateway stores user identity information. Access within Superblocks is then governed by the roles your admins assign. Each instance also has its own Identity & Access Gateway in its control plane. See Platform architecture. See Single sign-on to connect your identity provider.

Management plane

The management plane delivers platform upgrades to every instance. It triggers each upgrade and pushes it to a deployer that runs inside your instance. The deployer reconciles the environment and applies the upgrade. Superblocks plans, executes, and supports every upgrade, so your instance stays secure, supported, and current without your team planning, testing, or operating upgrades. In Managed BYOC, the deployer runs in your AWS account, so the management plane never applies changes to your account directly.

Superblocks Inference Gateway

The Build Agent sends its AI model requests to the Superblocks Inference Gateway, which Superblocks operates in Superblocks Cloud. The gateway applies only to the Build Agent. AI features in deployed apps use the provider you set in App AI. Every instance uses the gateway the same way, in both deployment models:
  • Outbound only: Your instance connects out to the gateway. The gateway doesn’t connect into your instance.
  • Encrypted and signed: Every request to the gateway is encrypted in transit with TLS 1.2 or higher and signed with short-lived AWS credentials.
  • Restricted access: The gateway accepts requests only from identities that Superblocks has authorized.
  • No prompt or response logging: The gateway doesn’t log or keep prompts or responses.
  • Zero data retention: Superblocks holds agreements with model providers so they don’t retain prompts or responses.
  • No training on your data: Superblocks holds agreements with model providers so your data is never used to train models.
  • Secure transmission: Data the gateway sends to inference providers is encrypted in transit.
Your AI prompt and response history is stored only in your instance. In Managed BYOC, that’s your AWS account, so Superblocks doesn’t retain your prompts or responses. In Dedicated Cloud, it’s stored in the environment Superblocks hosts for your instance.

Monitoring and analytics

Superblocks collects platform telemetry and product analytics from every instance in a central service, so it can operate the platform for you.
  • Platform telemetry: Logs, metrics, and traces from the services that run the platform. Personal and sensitive information is removed before it’s sent to Superblocks.
  • Product analytics: How features are used, so Superblocks can improve the product, including the quality of the Build Agent.
Superblocks uses this data to monitor platform health and reliability, validate upgrades as they roll out, and troubleshoot with your team during support cases. Access is restricted to authorized Superblocks personnel and audited, and Superblocks doesn’t use telemetry to train foundation models. Superblocks doesn’t collect app telemetry, the logs, metrics, and traces from the code your team writes. It stays in your single-tenant instance. See Telemetry.

Support access

Superblocks keeps the access it needs to support and debug your instance. In Managed BYOC, Superblocks has break-glass access through an admin support role in your AWS account. Superblocks assumes that role only in a break-glass scenario. The role grants elevated permissions for the resources the Superblocks platform owns, not administrative access to the rest of your account. See the Managed BYOC deployment guide.