Every enrolled agent signs in as itself. Every call is checked. You hold the record.
The questions a security lead asks about Ares, in that order: where the data goes, what each agent can act as, what is written down, and how you check it without trusting us.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
An AI agent security review tends to turn on four questions. Where does the data go? What can the agent act as? What is written down? Can we check it ourselves? This page answers each one for Ares and says where to see the proof.
What agents on Ares do. Agents on Ares do real work. They read orders, draft emails, update records and hand jobs to each other. That is why the review matters. An agent that signs in with a shared account and a password that never changes can do whatever that account can do, on any day. On Ares, each agent signs in as itself, and each job gets its own credential that covers that job only and then expires.
What changes for your team. You review one access policy, written so a person can read it, instead of the permissions spread across each integration. You choose which steps wait for a person. You hold a record of every decision, refusals included, and check it on your own machine. What is stored and what is not: security and data handling.
What the record shows your team for one job.
An illustration of a contract review, step by step, as your team would read it in the record.
- 01Documents
Issue a credential for this job: read the contract, write a summary, send the summary.
- Who approves
- No approval on this step
- On the record
- credential issued · read, summarise, send
- 02Documents
Read the services contract from the document store.
- Who approves
- No approval on this step
- On the record
- read-contract · allowed
- 03In-house tool
Fetch an outside web page for background. No permission covers it, so the call is refused.
- Who approves
- No approval on this step
- On the record
- fetch-page · refused · outside permission
- 04Email
Send the summary to the client. Client names and account numbers are taken out on the way.
- Who approves
- No approval on this step
- On the record
- send-summary · redacted · client identifiers
- 05Documents
Pass the indemnity clause to counsel. It waits for their review.
- Who approves
- Counsel
- On the record
- indemnity · approved by counsel
- 06In-house tool
The job ends and the credential expires. A later call with it is refused.
- Who approves
- No approval on this step
- On the record
- credential expired
In short
- Where does the data go?Where your deployment shape puts it: cloud, hybrid, or your own hardware with no connection out. On your hardware, the record stays in your building too.
- What can an agent act as?Only itself, with an identity from your directory. Each job gets a credential scoped to that job, limited in time, and narrower at each handoff.
- What is written down?Every decision: allowed, approved, redacted or refused, with the reason. Prompts, outputs and documents are not kept unless you turn on retention for audit.
- How do we check it without you?Export a job as a replay pack and run ares-verify, our open-source verifier, on your own machine. If a record was changed, the check fails.
Checks your team can run before the review meeting.
Built items run in the public sandbox today, with real agents on demo data. Designed items list their steps here. On request means we run it with you in the evaluation.
- Built
- We have run it.
- Designed
- The steps and approvals are designed. It has not run yet.
- On request
- We scope it with you before we design it.
- Built
Find the refused step
A send of a drawing to a new address is refused, and the reason is on the record.
Run it in the sandbox - Built
See a redaction on the way out
A contract summary leaves with client identifiers taken out. An outside fetch is refused.
Run it in the sandbox - Built
See a hidden instruction caught
An instruction inside a PDF is struck out before any agent reads it.
Run it in the sandbox - Built
Watch the permission narrow between companies
A supplier's agent reaches for the buyer's full bill of materials and gets only the line it was asked about.
Run it in the sandbox - Built
Verify a replay pack offline
Download the replay pack from any sandbox run and check it with the open verifier on your own machine. Edit the pack and run it again: the check fails.
Get the open verifier - On request
Revoke a credential in the middle of a job
Revoking a credential ends every credential derived from it. We show it in the evaluation.
The five guarantees
Every workflow on this page carries them. Each one has a limit, and we state it.
- 01
Each agent can do only what it was allowed to do, for that job.
The limit
Permissions are only as good as the rules you approve.
- 02
Sensitive steps go to a person.
The limit
You decide which steps are sensitive.
- 03
Documents are inspected before an agent sees them, and answers are checked before they leave.
The limit
Filters cover stated patterns and languages.
- 04
Every decision is recorded, including refusals, in a record an outside party can check.
The limit
It shows what agents did, not whether a business rule was wise.
- 05
It can run in your building, on one small machine.
The limit
Local models differ from the largest cloud models.
What it does not do
- It does not discover agents you have not enrolled. It sets the limits for the agents you register.
- It does not replace your identity provider. Your directory still says who each agent is.
- It connects to one identity provider product today. Others are on request, and the briefing confirms yours.
- It does not certify you. We map published guidance on AI agents to what Ares does, and your auditor decides.
Briefing, evaluation, licence.
Each step has a fixed scope and ends with something you keep.
- 01
Platform briefing
What Ares does, and how it fits your identity provider and the systems you already run.
- What you get
- A briefing for your AI, architecture and security leads.
- What you keep
- Agreement on one agent or workflow to evaluate.
- 02
Evaluation with one of your agents
One of your agents enrolled on Ares, with credentials, an access policy, a governed path and the record.
- What you get
- Your agent running on Ares, in your environment, at a fixed scope.
- What you keep
- Your own evidence that it works in your environment.
Fixed price, quoted after one call.
- 03
Licence and rollout
The platform in production, in the deployment shape you choose.
- What you get
- Onboarding for your teams. Solutions and delivery help where you want them.
- What you keep
- The platform in production.
The platform tiers on the pricing page.
Questions and answers
Evaluate Ares with one of your agents.
Bring one agent, one tool and the test cases your review needs. You keep the record of every run.
A senior member of the team replies within two business days.