Skip to content

Trust

The controls, and the gaps.

What a compliance review needs is a straight account of how the platform handles data and credentials, and an equally straight account of what it cannot yet evidence. Both are below.

Data residency

Where a workload runs is a recorded fact.

Compute runs in the region of the cluster it is scheduled onto, and the platform will not silently move it elsewhere for capacity.

For inference, each model carries an explicit jurisdiction and an in-region flag set by an operator — never inferred from the provider or the model name. An API key can be restricted to in-region models, so the boundary is enforced at the call rather than trusted to the caller.

Isolation

Tenants are separated by namespace, and by what a credential can name.

Each workspace owns namespaces on a cluster; a workload is scheduled into one and its service account is scoped to it. Nothing addresses another tenant's namespace by naming it.

Authorisation is checked per request against the workspace that owns the object, so a valid credential for one workspace is not a credential for another.

Encryption

Cluster credentials and provider keys are sealed at rest.

Kubeconfigs for registered clusters and credentials for upstream model providers are encrypted with AES-GCM under a master key held outside the database, and decrypted only for the request that needs them.

A database dump on its own is therefore not a set of working credentials. Key rotation is a supported operation with a documented runbook, not a migration someone writes under pressure.

Audit logging

Every state change is written down, including the refused ones.

Registering a cluster, minting or revoking a key, deploying a workload, changing a rate — each appends an audit record with the actor, the target and the outcome.

Failed attempts are recorded as failures rather than dropped. An access attempt that was denied is usually the entry an investigation is looking for.

What we cannot evidence yet

No third-party attestation, and no certifications.

ALYNREX holds no SOC 2 report, no ISO 27001 certificate and no independent penetration test result. The controls described above are ours, described by us, and have not been audited by anyone else.

If your procurement process requires one of those, we do not meet it today, and we would rather you learn that here than three weeks into a review. Tell us which one you need and we will tell you honestly whether it is on our roadmap and when.

Send a security questionnaire