The M-System

One operating system. Five connected products.

MIRAI OS provides the shared workflows, permissions, records and controls. Momentum, Milestones, Metrics, Mesh and Model give each audience and capability a clearly defined product surface. You do not need every product to start.

MIRAI OS governs. Momentum moves. Milestones engages. Metrics proves. Mesh connects. Model keeps intelligence under your control.

All five run on MIRAI OS Workflow · Context · Permissions · Approvals · Audit
01 · MIRAI Momentum · Staff operations

Keep every workflow moving.

One place for staff to see what needs action, what is waiting and what has already moved — with the relevant context already assembled by MIRAI OS. At a desk or on a phone: one product, every device, the same queue and the same accountability.

What it includes
Daily work queues, assigned cases and deadlines.
Prepared actions and drafts, ready for a person to send.
Approvals and exceptions, with a recorded reason.
Internal communication and operational history on the case.
See the foundation it runs on
Today
4 items
1 needs your decision
Harbour Group · 30-day termsPREPARED · AWAITING YOU
Site visit report · KestrelDRAFTED · REVIEW
Meridian renewal · call backSCHEDULED 14:30
Approve
One case, moving
Case created
Records checked
Next action prepared
Approved by a person
Systems updated

Illustrative. Sapphire = system action · bronze ◆ = human judgment.

02 · MIRAI Milestones · Stakeholder engagement

Keep every stakeholder informed and moving forward.

The same case, seen from the outside. Customers and external stakeholders track progress, provide information, complete actions and understand what happens next — without anyone having to chase, and without your staff fielding another status call.

What it is for
Current status and what is still outstanding.
Documents, payments, appointments and confirmations.
Support requests that land on the case, not in an inbox.
Fewer status calls, fewer chasing messages, one source of truth.

Industry-neutral at product level: parents, customers, clients, applicants, vendors, members, partners, patients, students. The configuration takes the audience word.

What the client sees Illustrative
Application · Northbridge
Stage 3 of 5
Details received
Identity verified
Deposit received
Proof of address needed
Upload document

The same case your staff see in Momentum — not a copy, and never out of date.

03 · MIRAI Metrics · Management intelligence

If it is not measured, we have not finished.

Metrics gives leaders a live view of workload, delays, ownership, performance and value against the baseline agreed before implementation. It is how a decision to expand gets made on numbers rather than impressions.

What it gives management
Executive dashboards across every workflow, not one at a time.
Trend analysis and variance against baseline, tracked continuously.
Capacity, cash and risk views, and operational benchmarking.
Exportable data, so the evidence is yours and not locked in.

The product is Metrics. The method stage is still Measure — map, move, manage, measure. Baseline measurement and audit history are part of MIRAI OS, not this product.

Measured against baseline · placeholders
Capacity
Baseline → result
Speed
Baseline → result
Quality
Baseline → result
Cash
Baseline → result

MIRAI publishes figures only when they are measured against an agreed baseline.

04 · MIRAI Mesh · Digital specialists and integrations

Every system and specialist, connected.

Mesh connects the systems, information and digital specialists that carry work across the organisation. Each specialist has a defined role, a defined access level, an action boundary and an approval limit — and hands to a person the moment it reaches one.

What it adds
Coordinated digital specialists — each configured to your rules, with a defined failure behaviour.
A reusable connector catalogue and advanced cross-system execution.
Escalation and recovery between specialists and people.
Integration observability — what ran, what it touched, what it changed.
You do not need Mesh to connect a system

The core connector framework, basic import and export, and the integrations your implementation requires are part of MIRAI OS. Mesh is for scale and coordination — see what is core and what is an extension.

Specialists on this workflow Illustrative
Records specialist Read · CRM, ledger

Retrieves and reconciles the case record across systems. No write access.

Correspondence specialist Draft only

Prepares the reply and the covering document. A person sends it.

Terms specialist Limit reached · escalated

Discount above 10% exceeds its approval limit. Handed to the account owner.

Ledger specialist Write · accounting

Posts the agreed entry once a person has approved the terms.

Every action is attributed and logged, whether a specialist or a person took it.

05 · MIRAI Model · Private intelligence infrastructure

Intelligence that remains under your control.

Open-weight and privately deployed models running in your tenancy, on your own hardware, or in isolated Singapore hosting we operate for you. Configured to your business — your terminology, your rules, your documents — and versioned when they change.

Why it matters commercially
Client records, contracts and student data need not be sent to a third party.
Data residency, stated in writing and enforced by the deployment.
Predictable cost at volume, without per-request pricing surprises.
Regulated and data-sensitive operations stay deployable.
How data and deployment work
Where it runs
Your tenancy

Deployed inside your own cloud account, under your identity and network controls.

On premises

Local hardware where policy, latency or regulation requires the data to stay in the building.

Hosted by MIRAI

Singapore hosting for companies that would rather we operated it — with the same boundaries in writing.

In all three, no third-party model provider sees your data. The point is custody.

The shared foundation · governs

MIRAI OS sits underneath everything.

Every product reads and writes the same operational state. Your team works the case in Momentum, your client sees the same case in Milestones, management reads it in Metrics — one set of rules, one audit history, and nobody working from a copy.

Workflow and state

Where every case is, what it is waiting on, and what happens next.

Rules and permissions

Who may see what, who may act, and where the boundaries sit.

Human approvals

The decisions that stay with a person, wherever they happen to be.

Audit and records

Every action attributed and logged, whether a specialist or a person took it.

See it working

The queue, the approvals and the audit trail, running on one workflow. MIRAI OS in detail ›

MIRAI OS Control

Most people experience MIRAI OS through Momentum, Milestones and Metrics. Authorised administrators use the control plane to configure workflows, rules, permissions, retention and approval limits.

What is core, what is an extension

Connecting systems and measuring results are not add-ons.

MIRAI connects the software you already run, and every engagement is measured against a baseline. Both are true whether or not you buy Mesh or Metrics — because the core of each sits in MIRAI OS. Here is exactly where the line falls.

Connectivity
Included in MIRAI OS
Core connector framework
Basic data import and export
The integrations your implementation requires
Event and workflow interfaces
Shared system records
Added by MIRAI Mesh
Multiple coordinated digital specialists
Advanced cross-system execution
Reusable connector catalogue
Agent-to-agent coordination
High-volume tool actions
Integration observability
Complex escalation and recovery
Measurement
Included in MIRAI OS
Audit logs
Workflow event history
Basic service metrics
Acceptance measurements
Pilot baseline reporting
Added by MIRAI Metrics
Executive dashboards
Cross-workflow analytics
Trend analysis
Value verification
Capacity and margin views
Operational benchmarking
Management reporting

You do not need every product to start.

Almost every engagement begins with one workflow, proved against its baseline. The rest is added when the workflow asks for it, not before.

Start with

MIRAI OS + Momentum + Metrics

One workflow in the system, proved against its baseline.

Add Milestones when

Customers, parents, applicants or vendors need to see progress, supply documents, make payments or confirm actions.

Add Mesh when

The workflow needs several coordinated integrations, digital specialists or cross-system execution.

Add Model when

Residency, private deployment, volume economics or model governance require it.

Start with the workflow, not the product list.

Tell us what is slow. We will tell you which parts of MIRAI it actually needs.

Map one critical workflow