Early access

Apply

Documentation
Documentation/Managing Your App/Security Posture

Security Posture

Which access controls Supero Cloud enforces as of 17 November 2026, the Content-Security-Policy state of app pages, where uptime history is published, and where to send SOC 2, penetration-test, DPA and SLA questions.

Security Posture as of 17 November 2026

This page lists what Supero Cloud enforces on production today. It was checked against the production configuration on 17 November 2026, and it gets a new date whenever one of these controls changes. Each row links to the page that explains the mechanism.
Every record carries its tenant in its address, and the runtime scopes every read and write to the caller's tenant. That holds for every app, including apps that serve a single organisation. The is_multi_tenant setting decides whether an app onboards many customer organisations into their own tenants. It does not turn isolation on or off.

Access Controls Enforced on Supero Cloud

ControlWhat a caller sees
Hidden fields in filters and sortsA filter or sort on a field the caller's role cannot read returns 400. The same per-role hidden set strips the field from responses. See Access Policies.
Filter operatorsA caller's read filter may use equality, a short operator allowlist and $and / $or / $nor. Any other operator returns 400 with error_code FILTER_NOT_ALLOWED.
Hidden fields on writesA value sent for a field that is hidden from the writer's role is dropped from the create or update.
References across tenantsA user without all-tenant access gets 403 when linking records across tenants. The source record must be in the caller's tenant. The target must be in the caller's tenant or in the project's default-tenant, which holds the app owner's shared records.
Explicit read denialsA read of a model whose rule for the caller's role says can_read: false returns 403 with error_code POLICY_READ_DENY. This covers get, list, query, aggregates, stats and reference lookups.
Models a policy does not nameIn apps created on or after 15 November 2026, when a role's policy sets default access to none, a read of a model that the policy has no rule for returns 403.

Who these checks apply to

The checks above apply to tenant-level roles, which is every end user of an app. Domain and project administrators, and project API keys, are not narrowed by access policies. That is the admin tier by design. An app's own server routes that read with the project key and pass rows to an end user apply the policy themselves.

API Keys and Tenants

A project API key reaches every tenant in its project. That is by design: it is the credential for building the app and for your own admin tooling. For an integration that acts for one customer, mint a key against that customer's named tenant. It resolves to tenant_user and reaches that tenant only. Security has the call and the check to run before you rely on the key.

Content-Security-Policy on App Pages

App pages deployed on Supero Cloud since 15 November 2026 send a Content-Security-Policy-Report-Only header with a nonce that changes on every response. In Report-Only mode the browser reports a script or style that the policy would refuse, and still loads it. An app deployed before 15 November picks up the header on its next deploy.
bash
curl -sI https://<your-app>.supero.live/ | grep -i content-security-policy

Uptime History and Incidents

supero.dev/status shows current service health, daily uptime measured by our own probe, and a write-up for each incident.

Connected Customer Databases

When an app reads or writes your own database through a live connector, every request that goes through Supero gets the checks on this page. Access that goes to the database directly, from your own services, reporting tools or administrators, does not pass through Supero and is governed only by the database's own permissions. Give the connector a database role limited to the tables it exposes, read-only for live_read. See Live Data, Read-Only & Security.

Where to Ask

QuestionAddress
SOC 2 status, a penetration-test report, an architecture review or a security questionnaire[email protected]
A Data Processing Addendum, or a Business Associate Agreement[email protected], copying [email protected]
The named subprocessor list[email protected]
A service-level agreement, backup and recovery objectives, or data residency[email protected]
A vulnerability report[email protected]
Certification status, the legal documents and the data-protection roles are on Compliance & Trust.