Security and data isolation
How Hyperstruck protects customer data through tenant isolation, encryption, and access controls.
In one line
Every tenant's data is isolated at the database level. Credentials are encrypted. Access is scoped by API key, organization role, and fine-grained authorization on agents and spaces.
Hyperstruck is built for teams that need to trust the platform with sensitive operational data: agent configurations, learnings from real workflows, and provider credentials. This page explains how the platform protects that data.
Tenant isolation
Every customer operates in a fully isolated tenant. Data isolation is enforced at the database level through row-level security (RLS) policies. Every table that stores customer data has an RLS policy that restricts access to the owning tenant. This is not application-level filtering. It is enforced by the database engine itself, which means a bug in application code cannot leak data across tenants.
Each API request is scoped to a tenant through the authenticated API key or portal session. The tenant context is set at the database connection level before any query executes.
Access control
Hyperstruck uses a two-layer authorization model:
- API key scopes — coarse capability checks (
agents:read,agents:execute,claims:curate, …) enforced on every route. - Fine-grained access — object-level permission checks on specific agents and spaces, backed by a Zanzibar-style authorization model.
Both layers must pass. Organization membership roles (owner, admin, developer, viewer) derive portal session scopes. Programmatic API keys carry explicit scopes with org-wide or per-space reach.
For the full permissions matrix, space kinds, API key scope reference, and separation-of-duty rules, see Access control (FGA and RBAC).
Credential encryption
Provider credentials (LLM API keys for OpenAI, Anthropic, Groq, and others) are encrypted at rest using AES-256-GCM with per-tenant encryption keys. The platform never logs, exposes, or returns credential secrets through the API. When you retrieve credentials through the API, you see metadata (provider, scope, status) but never the key itself.
Enterprise SSO
Enterprise customers can connect Hyperstruck to their identity provider so users authenticate through company-managed SSO. Organization roles sync from your directory into the tenant. This lets security teams centralise access, enforce existing identity policies, and offboard users from a single source of truth.
PII masking
Hyperstruck offers guardrails that detect and mask personally identifiable information before it reaches the LLM. This is available as an add-on for Pro customers and included for Enterprise customers. PII masking is configurable per agent and can be combined with prompt-injection prevention.
Rate limiting
API endpoints are rate-limited per tenant to prevent abuse and ensure fair access. Rate limits are enforced transactionally at the database level, not through an in-memory cache, so they remain accurate under concurrent load.
Infrastructure
Hyperstruck runs on managed cloud infrastructure with encryption in transit (TLS) and at rest across all storage layers. The platform does not store raw LLM conversation logs beyond what is needed for session history and learning extraction.
Related pages
- Access control (FGA and RBAC) for scopes, roles, spaces, and the permissions matrix
- Credentials API for managing provider credentials
- Agents API for API key authentication
- Pricing for details on which tiers include compliance features