New Revacom AppDefense × Atria — zero-trust governance for AI agents, now available across DACH. Read the announcement →
AppDefense — a division of Revacom

Autonomous Cyber Defense

The attacker is no longer a person at a keyboard. It is an autonomous agent that enumerates your estate, adapts to your controls and moves faster than any SOC rotation can answer. AppDefense fields the counterpart — and, with Atria, puts an enforceable boundary in front of every API an AI agent can reach.

AI agent governanceZero-trust gatewayPolicy as codeAppend-only audit logNIS2 & DORA evidence
New · Available now in DACH Revacom AppDefense × Atria

Admit AI agents to your APIs — under explicit, auditable control.

AI agents are already calling enterprise APIs: copilots, procurement tools, customer-service automation, integrations nobody formally onboarded. The usual choice is to block that traffic, which stops work, or allow it, which leaves no record of what an agent did, on whose authority, or within what limits.

Through a strategic distributor partnership with Atria Systems, Inc., AppDefense now offers a third option. Atria’s zero-trust policy gateway sits between the agent and the API and decides, request by request, what each agent is allowed to do — and keeps the evidence.

TerritoryGermany, Austria, Switzerland
AvailabilityWith immediate effect
DeploymentCloud, on-premises or air-gapped control plane
Delivered byRevacom engineers — implementation, policy design, operation, L1/L2 support
How it works

Identity, policy, decision, evidence — on every request.

Atria runs as a reverse proxy in front of the APIs you choose. Nothing changes in the applications behind it.

01

Identify

Every external agent receives short-lived zero-trust identity certificates and cryptographic tokens, typically valid for minutes. No shared secrets.

02

Bound

Permitted actions, parameters and rate limits are defined as policy-as-code, held in version control and reviewed like any other change.

03

Decide

Each request is checked against policy at the gateway. Atria targets policy decisions in under 5 ms.

04

Record

Allowed or denied, every request is written to an append-only log: agent, credential, endpoint, decision and reason.

Why it matters in Europe

Agent traffic has been the gap in your third-party evidence.

NIS2 and DORA expect you to show control over who and what can reach critical systems. Agents were not in that picture. Now they can be.

▸NIS2

Entities in scope must manage and evidence third-party access to network and information systems. Agent calls become attributable, policy-bound events.

▸DORA

Financial entities must demonstrate control over ICT third-party risk. The gateway log shows exactly what each external agent did, and what it was refused.

▸No SDK, no rewrite

No code change in the protected applications. Onboarding an API is a routing and policy decision, not a development project.

▸A preventive control, described honestly

Atria does not remediate. It stops an agent doing what policy does not allow — and proves it. Healing stays with the rest of the loop.

The wider division

What AppDefense does beyond the API boundary.

Atria is the enforcement point. Around it, AppDefense covers the rest of the estate.

▸Sentinel Agents

Autonomous defenders resident across endpoint, identity, network and application layers — continuously modelling what normal looks like in your estate.

▸Hostile-AI Detection

Behavioural signatures of adversarial agents: machine-cadence reconnaissance, adaptive evasion, prompt injection into your own copilots, agent-to-agent pivoting.

▸Autonomous Response

Isolate, revoke, quarantine, terminate — inside a policy envelope you author, with every action reversible and logged.

▸Heal, Not Just Stop

Compromised assets are handed to AppTimized for clean repackaging, patching and redeployment from a signed known-good baseline.

FAQ

Agent governance, answered.

What does Atria do?

Atria is a zero-trust policy gateway that sits in front of your APIs as a reverse proxy. It gives every external AI agent a short-lived cryptographic identity, checks each request against policy you write as code, and logs every decision — allowed or denied — with the reason.

Do we have to change our APIs or applications?

No. Atria requires no SDK, no backend change and no API rewrite. Traffic is routed through the gateway; the applications behind it stay as they are.

Where is it available?

Revacom offers Atria to organisations in Germany, Austria and Switzerland, with immediate effect. Revacom contracts with you directly and delivers implementation, policy design, ongoing operation and first- and second-line support.

Can the control plane run on our own infrastructure?

Yes. Atria is available as a cloud service or with an on-premises or air-gapped control plane, for organisations whose regulators or policies require it.

How does it help with NIS2 and DORA?

Both frameworks expect you to demonstrate control over third-party access to critical systems. Atria produces that evidence for agent traffic: which agent, with which credential, called which endpoint, what was decided and why. It is a preventive control and an evidence source, not a compliance certificate.

What does it cost?

Pricing depends on the number of protected hosts and the volume of agent sessions. Book a briefing and we will size it against your estate.

Find out which agents are already calling your APIs.

A 45-minute briefing: we map where agent traffic reaches your estate today, what a first policy would look like, and what evidence it would give your auditors.