AI agents for defence program leads, set out requirement by requirement.
For each requirement: what Ares does today, what needs configuration, and what it does not do. Planned work is labelled planned. Work is contracted under Beyond Aerospace Ltd., the company behind Ares.
A decade in defence and aerospace. In government procurement since 2016. The same technology since 2019, validated in US DoD and Canadian DND programs.
How this page is set out
A program office evaluates against its requirements, not against a feature list. This page takes the questions a program lead asks first, in that order. The table below gives each one a state. Where Ares does not meet a requirement, the row says so and says who does.
Who you contract with
Defence and government work is contracted under Beyond Aerospace Ltd., the company behind Ares. Ares Networks is a trade name of Beyond Aerospace Ltd. We send a capability statement on request. The people who brief your program office do the work and answer for it. The company page sets out the record from 2016.
Where the work starts
The first workflows we propose to a program office are of three kinds:
- requisition and procurement steps, with an approver on each order above your threshold;
- document handling across security domains, with redaction on the way out;
- back-office processes that pass through a reviewer, who signs each step.
One procurement request across a high side and a low side.
An illustration of the two-domain workflow. It is not in the public sandbox. We run it live for program teams, on the machine it ships on.
- 01ERP
A procurement request opens on the high side. The agent receives a credential for this request only.
- Who approves
- No approval on this step
- On the record
- credential issued · one request
- 02ERP
Read the requirement and the approved supplier record.
- Who approves
- No approval on this step
- On the record
- read-requirement · allowed
- 03Documents
Send the request to the low side for a price. Content above the low side's level is taken out on the way.
- Who approves
- No approval on this step
- On the record
- send-request · redacted · above receiving level
- 04Documents
Attach the full specification to the low-side request. That is outside the permission for this job, so the step is refused.
- Who approves
- No approval on this step
- On the record
- attach-specification · refused · outside permission
- 05Documents
Read the low-side answer at the door, before the agent sees it.
- Who approves
- No approval on this step
- On the record
- read-answer · inspected · allowed
- 06ERP
Raise the requisition against the budget line. It waits for the budget holder.
- Who approves
- Budget holder
- On the record
- raise-requisition · decided by budget holder
- 07In-house tool
Each side writes its own record of what crossed.
- Who approves
- No approval on this step
- On the record
- record · each side keeps its own
In short
- Does it meet our directives?We map each requirement to what Ares does today, what needs configuration and what it does not do. Your program decides whether that meets the directive.
- Does data stay in our country?On your own hardware, the site, the models and the record stay inside your boundary, with no outside link required. A hosted deployment keeps the record in the region agreed for it.
- Who signs the sensitive steps?A person your program names. The step waits until that person approves or rejects it, and both outcomes are recorded with the name.
- Can our reviewer check the record independently?Yes. The reviewer exports the record and checks it offline with the open verifier, on a machine that is not ours.
Workflows for a program office, with the state of each.
Built means the run is in the public sandbox today, on demo data. Designed means the steps are set out on this page or the linked page. On request means we scope it in the assessment.
- 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
Requisition with an approval threshold
The order is drafted and stock is checked. Above the threshold the order waits for the budget holder, and a change of supplier is refused.
Run it in the sandbox - Built
Purchasing under a written mandate
The mandate sets the ceiling, the approved merchants and the expiry. A merchant off the list is refused, and the credential closes at expiry.
Run it in the sandbox - Designed
Procurement request across two security domains
The workflow shown above. Redaction on the way to the low side, a refused attachment, and a record on each side. Not in the public sandbox; we show it live to program teams on request.
- Designed
Document control
A revised document checked against the register and routed for approval. Release waits for the named approver.
See the steps - Designed
Audit evidence for a review
The reviewer's request list answered inside the agreed scope. A read outside that scope is refused.
See the steps - On request
Correspondence and returns with a review step
The agent prepares each item and the reviewer signs it. Scoped with your office in the assessment.
The requirement, in the order a program office asks.
Requirements are stated in general terms. Your program supplies the exact wording, and we answer it line by line.
Data and processing stay inside the boundary
- State
- Does today
- What Ares does
- On your own hardware, a whole site runs on one small machine and keeps working with no outside link. The record stays on site.
- What remains with your program
- Providing the machine and the site, and deciding what may connect out.
A distinct identity for every agent
- State
- Does today
- What Ares does
- Each agent is enrolled with its own identity from your directory. No agent shares an account. It connects to one identity provider product today.
- What remains with your program
- Keeping the directory accurate. Confirming in the briefing that your directory is supported.
A person signs each sensitive step
- State
- Needs configuration
- What Ares does
- The steps you name wait for the person you name. Approvals and rejections are both recorded.
- What remains with your program
- Naming the steps and the approvers, and staffing the approvals.
Content above the receiving level does not cross
- State
- Needs configuration
- What Ares does
- Outbound content is inspected and redacted by the rules you set. The record names what was removed and why.
- What remains with your program
- Setting the rules for each domain. Filters cover stated patterns and languages.
An agent can be stopped from outside the agent
- State
- Does today
- What Ares does
- Your administrators revoke an agent in Ares. Every call it makes after that is refused, and the revocation is recorded.
- What remains with your program
- Deciding who may stop an agent, and when.
A record a reviewer can check independently
- State
- Does today
- What Ares does
- Every decision is recorded, refusals included. The reviewer checks an exported pack offline with the open verifier.
- What remains with your program
- Setting how long the record is kept and who may read it.
Certification or accreditation of your system
- State
- Does not do
- What Ares does
- The record is input to your assessment.
- What remains with your program
- The assessment, the accreditation and the sign-off.
Planned, not shipped: a named owner and review date for every agent, revoking every credential of a job in one action, and export of a credential in open formats.
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 certify or accredit your system. We map requirements, and the sign-off remains with your program.
- Only the on-prem shape runs disconnected. The hosted and hybrid shapes need a connection.
- It connects to one identity provider product today. Support for another directory is scoped on request.
- Local models differ from the largest cloud models. We state which model runs which step, and where.
Assessment, pilot, production.
Each step has a fixed scope and ends with something you keep.
- 01
Workflow assessment
A look at one process: where an agent can act, which steps go to a person, what a wrong action would cost, and what the data allows.
- What you get
- A short, paid look at one process, with your process owner.
- What you keep
- A written scope and a price for a pilot.
Fixed price, quoted after one call.
- 02
Pilot workflow
One workflow on your systems, supervised, with the record on from the first run.
- What you get
- One workflow at a fixed scope, with your people approving the sensitive steps.
- What you keep
- A working workflow and a measured result.
Fixed price, quoted after one call.
- 03
Production and run
The workflow in production on Ares, on your hardware or hosted in your country.
- What you get
- Support, and the next workflows.
- What you keep
- The workflow, and the record of every decision it made.
Recurring fee for operation and support.
Who else decides
Questions and answers
Tell us about one workflow.
Send us one requirement set and one workflow. We will answer the requirements in your order and state the scope of a first step. Fixed price, quoted after one call.
A senior member of the team replies within two business days.