Platform

Three components. Everything else stays yours.

Oathera answers two questions about every AI agent: what did it do, and does it have its DNA? Three Oathera components answer them. Your identity provider, your agents and the machines they run on, your MCP servers, your policy engine and your services stay yours.

Oathera's three components, and what stays yours Oathera's cloud holds the Oathera Identity Service. A dashed boundary marked yours holds your server or laptop, where your agent runs with its own key and the Oathera Witness, and your MCP server, which runs the Oathera MCP Plugin with its two capabilities, Oathera Agent Enrollment and Oathera Agent Enforcement. Your identity provider, your policy engine and your services are yours too. The agent calls your MCP server, the Witness reports to it, and the Oathera MCP Plugin works with the Oathera Identity Service. Oathera Identity Service keeps the record · in Oathera's cloud OATHERA Oathera Yours YOURS your server or laptop your agent its own key, kept here Oathera Witness your MCP server Oathera MCP Plugin Oathera Agent Enrollment Oathera Agent Enforcement identity provider policy engine services
The components

What Oathera is, and what stays yours.

Oathera is three components. Two run in your environment, on the machines where your agents run and with your MCP server. The third is Oathera's cloud. Everything else is yours, and stays as it is.

Oathera Witness

A small service on every machine where agents run: your servers and laptops. IT installs it. It watches the agents there from the operating system, and vouches for what it saw in a signed report that Oathera Agent Enforcement checks before policy uses it.

Oathera MCP Plugin

Two capabilities. Both run on your MCP server. Oathera Agent Enrollment gives each agent its identity: its own key, created and kept on its machine, the machine it runs on, and a named person who answers for it. Oathera Agent Enforcement checks every call: the identity token and a proof signed for that one operation. For an action that changes something, it also asks for a boundary decision, and without a valid one the call does not go through.

Oathera Identity Service (OIS)

Oathera's cloud. It keeps the record of every approved agent, compares the host at every token request, issues identity tokens, and answers Oathera Agent Enforcement with a signed boundary decision. Every decision is recorded, so you can answer what each agent did.

Stays yours

Your identity provider, where people sign in. Your agents and the servers and laptops they run on. Your MCP servers. Your policy engine. Your services and their data. Oathera works with them and replaces none of them.

How it works

Enroll. Check every time. Prove every call.

  1. Enroll. Oathera Agent Enrollment, on your MCP server, enrolls the agent: its own key, created on its machine, and the host. A person approves it before it acts, through your identity provider or the Oathera console.
  2. Check every time. Each time the agent asks for a token, the Oathera Identity Service compares the host with the enrollment record and refuses a mismatch.
  3. Prove every call. Oathera Agent Enforcement sits in front of your tools, verifies the proof the agent signs on its own machine for each operation, and asks for a decision before enforced calls. It verifies proofs for any tool you configure.
Oathera Agent Enrollment, Oathera Identity Service, Oathera Agent Enforcement, service Four boxes left to right: Oathera Agent Enrollment on your MCP server, the Oathera Identity Service that issues tokens and decisions, Oathera Agent Enforcement in front of your tools, and the service that receives a gateway assertion. Oathera Agent Enrollment agent, host, person Oathera Identity Service record, token, decision Oathera Agent Enforcement checks every call Your service gets a gateway assertion
Behind Oathera Agent Enforcement, your service gets a gateway assertion in place of the agent's token: a short, single-use statement that this one request passed.
What Oathera records and checks

A directory knows your agent's name. Oathera knows where it runs and who answers for it.

Oathera records the agent once, at enrollment

Your agent's DNA is what it is, where it runs, and who answers for it. The Oathera Identity Service holds it: what the agent stated about itself, the principal who approved it, what was found on its host, and its answers to the OWASP non-human identity questions when it sends them. Each identity token carries a summary of it as claims, which Oathera Agent Enforcement reads on every call.

Oathera checks the agent on every call

Your agent's fingerprint is on everything it does: its key digest, its host digest and the operation proof. A copy of the agent on another machine has a different host, so the same code and the same key file leave a different fingerprint.

Your side stays yours

The agent's keys stay on its host.

The anchor key is created on the agent's own host and kept there, in a file only the agent's user can read. The Oathera Identity Service receives the public key, never the private one. Each session key lives only in memory and is never written to disk.

  • Anchor key created and kept on the agent's host
  • Session keys in memory only
  • Anchor key held in a key manager or hardware module
Also in the platform

The rest of the picture.

Protected core

Both MCPs load a signed native library only after checking its signature, check it again while running, and stop if it has been changed. It runs in the hosted simulator.

Credential service

Records who approved what as verifiable credentials, when the Oathera Identity Service is set to issue them.

Oathera console

Sign-in with team roles, admin and viewer, and a step-up code to create a team. Live decision, posture and agent-risk views show what the MCPs report.

Run it in front of one real tool.

Design partners get a dedicated tenant, direct access to the founders, and a say in the roadmap.