Security

Your people data, isolated, permissioned and on the record.

Each organization's data is isolated in the database itself, every person and AI agent is limited to what their role allows, and changes go to an audit log the app cannot edit.

What you get

Controls you can check in a pilot.

01

Isolation in the database

Postgres row-level security, forced on every tenant table. The app connects as a role that cannot bypass it, and tests try cross-tenant access on every change.

02

Self-hosted sign-in

Keycloak runs as part of Ascend, over OpenID Connect. Every token's signature, issuer and audience is checked, and repeated failed logins lock out.

03

An audit log the app can't edit

Update and delete are revoked from the app's database role. Each row names the accountable person, and the agent if one acted.

How it works

Limits on the AI agents.

1

Your permissions, no more

An agent calls the same API a person does, with that person's own credentials.

2

Held above 10 people

Any agent action touching more than ten people waits for confirmation, at every setting.

3

Never unattended on people

Performance, succession and offboarding cannot be set to autopilot. The API and a database constraint both refuse it.

The difference

Every control, and how to check it.

ControlHow it worksHow to check it
Tenant isolationRow-level security, forced, on every tenant tableA second test organization sees none of your data
Access inside an organizationRole checks plus reporting-line checksSign in as an employee and open a colleague's record: refused
IdentitySelf-hosted Keycloak, OpenID Connect, lockoutThe realm configuration and the sign-in flow
Agent limitsPer-area dial, ten-person ceiling, three areas never on autopilotTry to set performance to autopilot: rejected
Audit trailAppend-only; update and delete revokedThe audit page and its CSV export, which logs itself
HardeningRate limits, security headers, non-root containersResponse headers on any page
Supply chainDependency audits and secret scanning block the buildThe CI configuration, on request
Questions

What buyers ask.

Where is our data stored?
In your organization's partition of Ascend's database, isolated by row-level security. Ascend is not yet hosted in a fixed region: where a pilot runs is agreed with each customer before any employee data is loaded.
Does our data leave Ascend?
Document search, reranking, tracing and role-play voices run on services Ascend hosts itself. The language model calls behind drafting, marking and the assistant go to Anthropic, so the text those tasks need does leave Ascend.
Do you hold SOC 2 or ISO 27001?
No. Single sign-on is OpenID Connect only, without SAML or SCIM yet. We would rather show you these controls working in your pilot than point to a badge we do not have.
How do we get the data processing agreement?
Email [email protected] with your organization's name and the contact who should receive it.

See it working on one of your own job roles.

A 30-minute call. Send two or three documents for one role, and watch Ascend turn them into an onboarding plan, training and a check that people understood it.