M365-Benutzer anlegen
Risiko: HochWorkflow · Kollegen-Onboarding
Governance is part of the product core.
Controlled autonomy means clear approvals, technical boundaries, and verifiability in a security review.
nordnung.ai · audit.log
> session start: ticket #4821
instance isolation verified ✓
AUDIT: dedicated instance · data center DE
> request credential: exchange
vault injection to approved asset ✓
POLICY: no plaintext passwords in LLM context
> execute action: mailbox permission
security agent: four-eyes check passed ✓
approved by admin@customer.com ✓
AUDIT: signature + method call recorded
> kill switch available
session can be stopped anytime ✓
Nine commitments, all verifiable.
Each commitment maps to a control point in the audit log.
- ✓Hosted in GermanyDedicated instance per customer
- ✓Instance isolationData & execution separated
- ✓Credentials in VaultAES-256, approved assets
- ✓Passwords never in plaintextCredentials engine
- ✓Four-eyes principleSecurity agent reviews every action
- ✓Audit logIntegrity-checked, per step
- ✓Kill switchStops instantly
- ✓EU model routingEU regions only
- ✓DPA & security reviewReview on request
Approvals before anything happens
Every pending action lands in one inbox, sorted by risk. In operating mode 1, no step runs before an admin has approved it.
Try it: approve or reject, just like in the platform.
From 1,348 analyzed support tickets we know: automatable tickets hold 56% of our support hours. The decision when that happens stays with a human.
nordnung.ai · approvals-inboxSchematic view · German product UI · demo data
Offene Freigaben (3)
Diagnose-Skript am Arbeitsplatz ausführen
Risiko: MittelGerät · FIN-PC-04
SharePoint-Liste lesen
Risiko: NiedrigWorkflow · Lizenz-Übersicht
Autonomy is deliberately staged
It grows with the IT team's trust: from the first approval to solving on its own.
Operating mode 1
A tool for IT. The team operates nordnung; every relevant action requires approval.
Operating mode 2
nordnung acts on its own, but with tight approvals in a defined user context.
Operating mode 3
nordnung answers calls, resolves on its own, and escalates when needed.
Data flow and providers
Intake, controlled execution, and feedback are separate paths. Not every piece of information reaches every path.
Wrapper actions instead of free code or shell execution; least privilege per agent, scope, and endpoint.
Audit and operational data retained only as long as needed for traceability and support. Details in DPA and review.
Goal: maximum independence from external providers; open-source principles as the strategic core.