Permissions, audit, data boundary
Roles down to buttons, every action audited, data stays in your building.
Permissions, auditing and data boundaries are enforced server-side.
Permissions down to the button
RBAC covers menus, pages and buttons. Hiding a button is not security; the server is the only authority. AI actions reuse the same permissions.
- Roles for menus, pages and buttons
- Server-side checks, frontend only presents
- AI actions bound by the same rules
- Out-of-scope requests return 403 and are logged
Every action leaves a record
Sign-in, configuration changes, batch runs, releases, rollbacks and AI actions all land in audit, with actor, time, parameters and result.
| Action | Recorded |
|---|---|
| Sign-in | Account, source, result |
| Configuration | Before, after, actor |
| Batch run | Targets, command, output |
| Release and rollback | Version, environment, result |
| AI action | Session, action, parameters, result |
Data boundary
Capture happens locally; raw payloads need not leave the host. Data is stored in your own building, and the platform does not require a vendor connection.
Session replay supports input masking and field-level blocking.
Bring your system in
Tell us what you run: OS, kernel, public network or not, virtual machines or clusters. We will map the path in.