ProductOverviewHow It WorksCapabilitiesFor Your Team
TrustOverviewData Protection & GovernanceSecurity & AccessOwnership & ConfidentialityAudit & Accountability
ResourcesTechnical OverviewAPI OverviewSupport
CompanyAbout AscentMLContactRed Mountain Innovations
Talk to AscentML

Isolated by design. Controlled by permission.

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.

Customer isolation at every layer

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.

1Application

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.

2Database

Least-privilege service accounts

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.

3Storage

Scoped file access

Stored files are organized by tenant. Signed URLs are limited to one object, one tenant, one action, and a short expiration.

Access that matches responsibility

Role-based permissions

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.

User-scoped API keys

  • Belong to an individual user
  • Never exceed that user’s permissions
  • Can be restricted to specific projects or models
  • Support per-key quotas and analytics
  • Can be rotated or revoked at any time

Sign-in protection

  • Sign-in scoped to your organization’s customer identifier
  • Password complexity requirements
  • Progressive lockout after failed attempts
  • Failed sign-ins recorded as audit events
  • Sessions invalidated after a credential reset

Session protection

  • Secure, HTTP-only cookies
  • SameSite and CSRF protections
  • Session expiration
  • Server-side revocation

Credentials and encryption

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.

Privileged access is the exception, and it is recorded

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.

What is not available yet

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.

Bring your security review to us

We are prepared to walk your security and IT teams through customer isolation, access controls, credential handling, and current limitations.