The checkpoint runs in your company. The AI never holds your passwords.

Architecture

What runs where

Calls that only read are checked against the limits too, but need no ticket. Only actions that change something need one.

Data

What leaves your network

• To the AI provider: what the AI reads and writes through its tools, for example the ERP records it looks up. That is no different from using that AI today. To keep it inside your network, use a model you host yourself.
• To the Authority Server: who acted, under which permission, the kind of action, the details checked against the limits such as amount and recipient, the running totals and the time. Never a password. For a message, a fingerprint of its content, not the content itself.
• To Suveren: only during the first three weeks, while we host the Authority Server, in Frankfurt, under a data processing agreement. After that, nothing.

People

Who approves, and how

People log in to the Gateway with their Suveren account. Each area, such as payments or email, has its own approvers. When an action needs a yes, the Gateway shows the request with everything needed to decide. The person approves or rejects it there, and their name goes on the ticket.

For each area, the person who gives the permission chooses one of three ways:

• Runs on its own: within the limits, every call gets its ticket and runs without asking anyone. The limits include amounts, recipients, systems, and daily and monthly totals across all calls.
• Asks first: every call becomes an approval request showing the full action. Nothing runs until an approver says yes. A request that nobody answers expires after 72 hours; requests are kept seven more days, then deleted.
• Asks above a limit: below the amount you set, the call runs on its own; above it, it becomes an approval request as above. Above a fixed ceiling your team sets, nothing runs and no one can approve it.

Who may approve is set per area by your team's administrators. Being a member of the team alone does not allow anyone to grant permissions.

The ticket

What a ticket contains, exactly

Every ticket contains:

• Who allowed it: the person's permission, and their name where their identity is verified.
• What: the kind of action and the system it runs in.
• The details checked against the limits, for example amount and recipient.
• The running totals for the day and the month, and the limits that applied.
• The approval, if someone had to say yes first.
• For a message: a fingerprint of its content, not the content itself.
• The time, and the Ed25519 signature that proves nobody changed it.

Anyone with the public key can check a ticket, without Suveren and without a network connection. The Gateway keeps its own signed copy of every ticket, and your auditor can export them.

A ticket never records how fast or how well anyone works. Who may read tickets and how long they are kept is agreed with your works council.

Running it

What your team runs

Updates come as numbered releases. For as long as Suveren offers the service, updates and security fixes for the unmodified software are free, and we give twelve months' notice before that ends. How many days of your team's time each step takes depends on your systems; we estimate it with you in the thirty-minute call.

Who stands behind it

One person behind it, and what you need to carry on without him

Suveren is a program and the work of bringing it into a company. Andreas Schadauer developed the program and does that work, with a network of partners. He described the protocol, the what and the why. AI wrote the software, the how, under his direction. Automated tests check it, including a test suite for the open-source protocol that runs against the real programs.

If Suveren stops, you keep running. The Gateway is open source, you hold the Authority Server's source code, and the protocol is open source.