Your AI agents.
Under your control.
Kommit gives security and engineering teams the visibility, access controls, and audit infrastructure to deploy AI agents without losing sleep. Every section below is marked live today or design-partner roadmap so you know what's reproducible right now.
Every privileged admin action logged — automatically.
Hash-chained admin audit trail for every privileged admin action in the platform. Exportable as JSON or CSV for procurement. Cron sweeps verify the chain still verifies.
LiveHumans in the loop when it matters.
Approval gates for sensitive actions are in design-partner pilots — deploy promotions, send-email tools, payment writes. Today: org-level admin approvals on workspace mutations.
RoadmapPermissions scoped to the workflow, not the org.
Per-workflow RBAC + SSO + separation-of-duties is on the design-partner roadmap. Today: Better Auth org-level roles + connection-level Postgres RLS enforcing the tenant boundary.
RoadmapA complete, immutable record of every privileged admin action in your workspace.
Every privileged event is signed with an HMAC linked to the previous one. If anything is tampered with, the chain breaks — and the cron sweep flags it. Export as JSON or CSV for your auditors. Per-tool-call granularity (agent runtime events) is the design-partner roadmap.
Connection-level boundary today. Per-workflow RBAC in design.
Postgres enforces the tenant boundary at the connection level — no app-code path can downgrade it. The full per-workflow RBAC matrix below is the design-partner destination; today the platform runs on better-auth org roles + the RLS enforcement above.
MIXED — SEE BADGESSSO + SCIM
Okta, Entra, Google, Ping. Auto-provision members on your verified domain, JIT access. Better Auth SSO integration in design-partner pilots.
Connection-level RLS
App code connects as a NOBYPASSRLS Postgres role; the database itself filters every read by tenant. Verified at boot against pg_roles so a misconfigured deploy can't downgrade silently.
Builder ≠ Deployer
Per-workflow promotion gates so builders can compose and test but only Owners + Admins can promote to production traffic. Pilots running with design partners.
Column-level secret storage
Stored secrets — like project environment variables — are encrypted at the column level (AES-GCM); the ciphertext is never written to logs or surfaced in API responses. Encrypting OAuth tokens at rest + BYOK are on the roadmap.
Your data stays in your region. PII redaction is in design.
Workspaces are pinned to a region at creation. PII / PHI redaction before model calls is part of the design-partner roadmap — today, data residency is the live guarantee; redaction policies are the work this section describes.
Raw document or message
Customer contract, support ticket, invoice — whatever your workflow ingests. Stored in your chosen region (today: eu-central-1).
eu-central-1 · livePII / PHI stripped before model call
Names, emails, account numbers, health codes — detected and replaced with typed tokens before the prompt is assembled.
in designApproval before sensitive actions
Actions you've flagged sensitive — send email, execute payment, update record — pause for human review before executing.
in designResult captured in audit trail
The final output, post-approval, is logged with a full lineage record: inputs used, model called, who approved, when.
hash-chained · liveEU · Frankfurt today
All workspace metadata, vector indices, and audit events live in Hetzner eu-central-1. UK, US, APAC regions are roadmap — file with design partners if you need a specific region day-one.
Zero-retention model contracts
Calls to hosted Anthropic + OpenAI models run under their respective zero-retention agreements. Your prompts and outputs are never used to train their models.
Deploy in your VPC
Customer-managed VPC + BYOK + on-prem distribution are on the design-partner roadmap. Same control plane, different deploy substrate.
Policies enforced at runtime, not documented after the fact.
The policy library binding agents to runtime enforcement is on the roadmap, scoped with design partners. The six policy types below are the destination model: attach policies to agents and workflows directly, and the runtime blocks violations before they execute.
DESIGN PARTNER ROADMAPRate & quota limits
Cap model spend, token throughput, or API calls per agent per day. Enforced before the call is made.
Data class restrictions
Prevent agents from accessing or returning specific data classes — PHI, PII, PCI controlled per workflow.
Tool allowlists
Specify exactly which tools and integrations an agent may call. Everything else is blocked at the runtime layer.
Output content filters
Block outputs that match regex patterns, semantic categories, or classification labels before they reach downstream systems.
Model allowlists
Control which foundation models agents are permitted to call. Switch models in staging without production access.
Geographic restrictions
Prevent workflows from calling external services or models outside approved regions. Enforced at the network layer.
When something goes wrong, you can find it in minutes — not days.
Anomaly detection & alerting
Kommit will monitor token spend, error rates, unusual tool calls, and policy violations in real time. Alerts route to Slack, PagerDuty, or your SIEM.
- →Spike in model spend from a single agent
- →Tool called outside its allowlist
- →Repeated policy violations in a run
- →Human gate bypassed or timed out
- →Output matched blocked content pattern
Disable a workflow in one click
Pause or disable any workflow immediately from the control plane. Then trace the incident backward through the audit log — every event, every input, every decision in sequence.
- →Isolate the affected workflow without touching others
- →Replay any run step-by-step from the audit trail
- →Export the full lineage record for your incident report
- →Roll back to a previous workflow version
- →Re-run with a fixed policy after root-cause analysis
What security teams ask us.
admin_audit_logs with an HMAC chain — change any record and the chain breaks. Export as JSON or CSV from the admin panel. A cron sweep re-verifies the chain on a schedule.No SOC 2 badge. No HIPAA BAA. No EU AI Act conformity.
Kommit ships control libraries that map to these frameworks; your audit, your certification. We provide the evidence trail. For the full compliance posture map and procurement-grade docs, see the Trust Center.
Not a Kommit certification
We ship a control library mapped to Type II criteria + evidence trails baked into the platform. The Type II audit is yours; the evidence belongs to us.
No BAA yet
PHI redaction primitives are roadmap; audit logs are live. We do not yet sign Business Associate Agreements. Covered entities should not rely on Kommit for PHI processing today.
Processor, not certified
EU operations + EU sub-processors. We act as a data processor under your DPA. We are not ISO 27701 certified and don't claim to be.
Controls, not conformity
Risk-classification + human-oversight primitives are in design-partner pilots. We are not a registered conformity assessment body — customers classify and register their own workflows.
See it on your stack.
30 minutes with our team. We'll walk you through governance, audit, evals — and answer everything procurement will ask. Bring your own NDA; we'll sign in 24 hours.