The platform
One platform. AI agents that work, and proof that they did.
Ayion Meru runs agents on bounded work inside your systems, and records, approves and reconciles every consequential action, whichever vendor’s agent took it. Both halves sit on one core. Everything else plugs in.
What it is
Three parts. One core.
Meru Run does the work. Meru Assure proves it was done. Core is the small layer underneath that both stand on, and the layer everything else plugs into.
Why we build one platform underneath-
Core
The small layer underneath.
Identity and policy, the capability registry, durable execution, the model gateway, the evidence ledger and capture. Six pieces, and nothing else.
Read the architecture -
Run
Agents, packs, the workspace.
Agents complete bounded work inside your systems under an operating contract. Business Packs bring the workflows, roles, metrics and policy defaults. A daily workspace shows people what is waiting on them.
How Run works -
Assure
Controls, approvals, reconciliation.
Business-level controls on every consequential action, approvals bound to the exact parameters, each action checked against what actually changed, and evidence packs an auditor can read without us.
How Assure works
A stack in three bands. At the top, JhiOn for longevity and health span sits beside a dashed box for future vertical platforms in insurance, gaming and healthcare administration. Both feed into the middle band, Ayion Meru, which holds Run with its agents, packs and workspace beside Assure with its controls, evidence and reconciliation, and Core beneath the pair carrying identity, policy, the ledger, durable execution, the model gateway and capture. From Core, dashed lines drop to four plug points: models from any provider, agents whether Ayion’s, a partner’s or external, business systems reached through connectors and change feeds, and packs and controls for a department or an industry.
One action, end to end
The same path, every time.
Every consequential action follows the same path, whether an Ayion agent, a Microsoft or Salesforce agent, or one you built took it. Policy first, then an approval bound to the parameters where one is needed, then execution, the observed change, reconciliation, and a record at the end.
A spine runs left to right. The agent proposes an action with typed parameters and declared side effects; a policy check evaluates the controls against the request; the action executes in your system once, with retries; the platform observes the change in the system of record; and reconciliation compares what was intended against what actually happened. Two detours leave the policy check. Upward, an action that needs sign-off goes to an approval bound to the parameters and the record version, and drops back into execution once it is approved. Downward, an action that is blocked, or an approval that is declined, lands in a box marked stopped, with the reason. Both the stopped box and reconciliation lead into one evidence record at the foot of the drawing, holding identity, policy, approval, execution, observation, reconciliation and integrity.
Autonomy
Autonomy is chosen per action.
Not per agent, and not once. An agent can categorise tickets on its own, draft customer emails for approval, and have no refund permission at all.
One agent, five modes, set per action type rather than per agent.
| Mode | What the agent may do | Example |
|---|---|---|
| Observe | Reads and surfaces what it finds. Changes nothing. | Lists the tickets that will breach their response time today. |
| Recommend | Proposes an action and shows the evidence behind it. A person decides. | Suggests the category and the owner for a new ticket. |
| Prepare | Drafts the work and stops. Nothing leaves without a review. | Writes the reply to the customer and leaves it unsent. |
| Execute within limits | Acts inside limits authorised in advance: record type, amount, rate and budget. | Categorises and routes tickets on its own, with no refund permission at all. |
| Escalate | Routes the case to a named person, assembled, with the trail attached. | Hands a refund request above the limit to the duty manager. |
Pluggable at six points
Swap the parts. Keep the platform.
Models, agents, systems, packs, controls and channels each plug in through a published contract. Change one and nothing above it is rebuilt.
What each plug point accepts. The packs and integrations page carries what is live and what is planned.
| Plug point | What plugs in | Through |
|---|---|---|
| Models | Language, embedding, vision and speech models from any approved provider, or your own credentials. | The model gateway, routing by capability, cost and data location. |
| Agents | Ayion agents, partner agents, agents you built, whole external agent systems. | Operating contracts, MCP, A2A adapters and the capability registry. |
| Systems | ERP, CRM, billing, support, HR, data warehouses and custom APIs. | Connectors, MCP servers, event feeds and change feeds. |
| Packs | Department packs for finance, customer operations and procurement; industry packs for longevity and health, financial services, insurance and gaming. | A versioned pack format declaring workflows, controls, mappings and tests. |
| Controls and policies | Control templates, framework mappings and your own policies. | Policy-as-code and versioned Control Blueprints. |
| Channels and interfaces | Slack, Teams, email and mobile approvals; REST, events and MCP outbound; the auditor portal; GRC and SIEM exports. | Channel adapters and signed exports. |
A hub. The Meru Core sits in the middle as the smallest thing in the picture, labelled small on purpose, with six discs around it, each on its own spoke and joined to nothing else: models from any provider, agents whether Ayion’s, a partner’s or external, systems reached through connectors and change feeds, packs for a department or an industry, controls written as policy-as-code, and channels carrying approvals and exports.
The independence rule
The doer does not keep the record.
One company offering both halves only works if the half doing the work cannot touch the half keeping the record. So it cannot.
Assure keeps its own ledger. Run cannot write to it, keys stay with you, and any third party can verify a record without Ayion. You can buy Assure on its own.
Who it is for
Three readers. Three pages.
The platform is one thing, but nobody buys all of it at once. Start where your job starts.
-
Operations
“Show me which of my work an agent can safely take on.”
Heads of operations, finance operations and customer operations. Run holds the operating contract, the packs, the workspace and the autonomy ladder.
Read Run -
Controls
“Prove to my auditor what the agents did.”
Controllers, internal audit, risk and compliance. Assure holds the controls, the bound approvals, reconciliation and the evidence packs.
Read Assure -
Technology
“Tell me whether this plugs into what we already run.”
CTOs, platform and security leads. The architecture page holds the core components, the capture paths, data handling and deployment.
Read the architecture
Packs
The work arrives in packs.
A pack is a versioned bundle of workflows, agent roles, controls, mappings, metrics and tests for one department or industry. Install one, plug in your systems, and start in observe mode.
The pack catalogue-
Available in pilot
Finance operations
Overdue invoices chased, vendors paid, journals prepared, and every step evidenced.
-
Available in pilot
Customer operations
Refund limits, credit limits, and written commitments that need an approval before they are sent.
-
Planned
Procurement
Supplier evidence collected, comparisons prepared, and purchase controls applied before an order leaves.
-
Planned
Longevity and health
Health-span plans, check-ins and follow-ups under a person’s oversight. JhiOn is the vertical platform built on this work.
See JhiOn
Start with one pack and ninety days.
A paid pilot on your systems, your agents and your work, beginning in observe mode. Each phase ends in something you keep.