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.
Controls you can check in a pilot.
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.
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.
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.
Limits on the AI agents.
Your permissions, no more
An agent calls the same API a person does, with that person's own credentials.
Held above 10 people
Any agent action touching more than ten people waits for confirmation, at every setting.
Never unattended on people
Performance, succession and offboarding cannot be set to autopilot. The API and a database constraint both refuse it.
Every control, and how to check it.
| Control | How it works | How to check it |
|---|---|---|
| Tenant isolation | Row-level security, forced, on every tenant table | A second test organization sees none of your data |
| Access inside an organization | Role checks plus reporting-line checks | Sign in as an employee and open a colleague's record: refused |
| Identity | Self-hosted Keycloak, OpenID Connect, lockout | The realm configuration and the sign-in flow |
| Agent limits | Per-area dial, ten-person ceiling, three areas never on autopilot | Try to set performance to autopilot: rejected |
| Audit trail | Append-only; update and delete revoked | The audit page and its CSV export, which logs itself |
| Hardening | Rate limits, security headers, non-root containers | Response headers on any page |
| Supply chain | Dependency audits and secret scanning block the build | The CI configuration, on request |
What buyers ask.
Where is our data stored?
Does our data leave Ascend?
Do you hold SOC 2 or ISO 27001?
How do we get the data processing agreement?
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.