Tenant context required
Every customer-owned record is tied to its tenant, and every customer-facing query is required to filter by it. Requests without tenant context are not permitted.
Every customer operates in its own private, isolated environment. Every request is checked against that environment and the permissions of the person making it.
Credentials are protected, data is encrypted, and privileged access is recorded.
Each organization’s private environment—known technically as a tenant—is kept separate from every other customer’s. Cross-customer data access and sharing are prohibited.
Isolation is not a single control. It is applied consistently wherever customer data is stored or processed.
Every customer-owned record is tied to its tenant, and every customer-facing query is required to filter by it. Requests without tenant context are not permitted.
Customer-facing services, the inference runtime, and internal tooling use separate database roles with only the access each one needs. Internal experimentation data is never readable by the customer runtime.
Stored files are organized by tenant. Signed URLs are limited to one object, one tenant, one action, and a short expiration.
Access is controlled by permissions, not hard-coded user types. Your administrator assigns roles to users, and each role carries a defined set of permissions.
Experience settings change what a user sees. They never change what a user can do.
Secrets are stored in a form that cannot be read back.
Passwords are stored using an adaptive hashing function with a unique salt. Sessions, activation tokens, and API keys are high-entropy random values stored only as hashes.
An API key is shown once, when it is created. After that, only a short identifying prefix is visible. Keys never appear in application logs.
Data is encrypted in transit with TLS and at rest in both database and file storage. Infrastructure credentials are held in a managed secrets service.
AscentML staff may occasionally need to access a customer environment for support, troubleshooting, or recovery.
That access requires elevated internal authorization, a stated reason, and shorter session durations. The interface clearly indicates when elevated access is in use.
Every privileged action is written to the audit history.
Single sign-on (SSO, SAML, and OIDC) is not part of the initial release. It is on the roadmap.
The platform currently runs as hosted SaaS in a single production environment. Dedicated customer environments and multi-region hosting are future considerations.
We are prepared to walk your security and IT teams through customer isolation, access controls, credential handling, and current limitations.