Compliance
you can actually operate.
Set rules, decide what needs approval, choose what gets recorded. All in one interface a compliance lead can run without IT, and one that binds on every run instead of afterwards.
New policy
Describe it in a sentence, or build it in the editor.
Devctrl proposes this rule from it:
Applies toAll teams · every external tool · live immediately
How a policy comes about: write a sentence, check the rule, save it.
Onboarding
Ready in four steps.
Not an integration project. You set this up in a morning.
11 · Create teams
Finance, Legal, Sales. Rules hang off the team, not off individuals.
22 · Choose the rules
From templates built for regulated industries, or your own. In plain words, not as a script.
33 · Approve connections
You approve which systems may be used. Connecting is still each person's own account.
44 · Set the recording depth
Per team, with its own retention. From then on every run records itself.
Security
Four things that are not negotiable.
Not as a promise, but as how the system behaves.
- Own credentials, never a shared account
- Every run uses that person's rights. What they may not do, they may not do with AI either.
- Sensitive data is masked
- Bank details and personal fields are replaced before a model ever sees them.
- Anything critical stops
- Amounts, external recipients, write access: the run pauses and waits for a human.
- The record is only ever added to
- Nothing in the product rewrites a decision after the fact, and changing what gets recorded is itself recorded, with your name on it.
Reconcile the July supplier invoices · Finance
- Marco Feld started a task
Under his own DATEV access, not a shared robot account
- Read 42 invoices from DATEVAllowed
Inside the permissions Finance already granted him
- Supplier bank detailsRedacted
Masked before the model ever saw them
- One payment above €10,000Needs approval
Held for a second pair of eyes
Evidence
The folder an audit asks for.
Two views answer the two questions an audit actually asks: what do you record, and what happened on this one run?
Recording posture
Per team, with retention set independently
| Scope | Capture | Retention | Chains · 30d | With content | Policy events |
|---|---|---|---|---|---|
| Finance | Everything | 90 days | 1,284 | 1,284 | 22 |
| Legal | Everything | Kept indefinitely | 412 | 412 | 3 |
| Sales | Activity only | 30 days | 3,160 | 0 | 51 |
| Support | On policy events | 180 days | 2,075 | 18 | 18 |
We'll walk it through with your compliance team.
30 minutes, your requirements, concrete answers.