Capability map · Overview
The mAIstro platform at a glance.
What the platform does, how it works, what it runs on — with the principles it was built on and the services that surround it. Click any block to open its detail.
A pre-built agentic AI system you configure
Three levels of capability, held together by governance and differentiators — with two services that wrap around it.
The three levels stack top to bottom: what you see, how it works underneath, what runs it. Above and below sit the platform's promises — the reason answers can be trusted and the levers that actually move the business. On either side, the services that get you there: assessing what you have, and modernising into what you'll run.
04 · Governance
What makes it safe
Trust
Consistency
Integrity
06 · Service
Data assessment
- Estate discovery
- Quality baseline
- Evidence trail
Read→
01 · Level one
Open →
What it does
Dashboards
Ask in plain English, get a live dashboard.
Workflows
End-to-end automation at a fraction of the cost.
Agent orchestration
Picks the right agents and runs them in order.
02 · Level two
Open →
How it works
Telemetry
Full telemetry out of the box.
Reusable results
Every output is queryable and auditable.
Multi-tenant
One platform, many clients, from day one.
03 · Level three
Open →
What it runs on
Model & tool access
Any model, any database, no rebuild.
Control plane
PostgreSQL holds state and permissions.
Iceberg
Open, client-owned tables underneath.
07 · Service
Planning & modernisation
- Target architecture
- Sequenced roadmap
- Delivery at pace
Read→
05 · Differentiators
What moves the number
Optimisation
Agnostic
Acceleration
How to read the map
The three levels
Stack, not silo
Each level supports the one above. Dashboards depend on workflows. Workflows depend on orchestration. Orchestration depends on the runtime. Buying one level without the others is where most agent projects go wrong.
The two promises
Safety and impact — both, always
Governance sits above every level so nothing runs that shouldn't. Differentiators sit below so every capability is measured against whether it actually moves the number. Without both, you have a tool. With both, you have a platform.
The two services
What we do around the product
Data assessment maps what you have and what you can trust. Planning & modernisation designs the target and delivers the move. The platform is the product; the services get you onto it in two to three weeks, not two to three quarters.
01 · Level one · What it does
What the platform does.
The top of the stack — what your teams actually see and use. Three capabilities that turn a natural-language question into a live dashboard, a running workflow or a coordinated multi-agent action.
Live
01.1 · Capability
Dashboards
Ask in plain English, get a live dashboard.
Ask in natural language and the dashboard builds itself, with recommendations on what to look at next. No dashboard templates to maintain, no BI backlog to work through — the question is the dashboard.
What it means for you
- A CFO can ask “show me DSO drift by customer this quarter” and get the answer, live, with the drill-down already in place.
- Dashboards are composed at the moment of the question, not built ahead of time.
- Every element cites its source; every figure is queryable.
Live
01.2 · Capability
Workflows
End-to-end automation at a fraction of the cost.
Automates processes end to end — the same work done at a fraction of the cost. A workflow is not a bot: it is a repeatable, auditable sequence that agents run, and humans approve at the points that matter.
What it means for you
- Reconciliation, renewals, exceptions, triage — the shapes of work that never quite fit an RPA tool.
- Each run is a first-class object: reviewable, replayable, comparable.
- New workflows compose from the same agents; you don't hire per workflow.
Live
01.3 · Capability
Agent orchestration
Picks the right agents and runs them in order.
Breaks a request into steps, picks the right agents and tools, runs them in order and checks the result. The orchestrator is where mAIstro earns its name — coordinating specialists so the whole runs like one system.
What it means for you
- You don't wire agents together by hand — the orchestrator selects and chains them.
- Every run produces a trace: what was called, in what order, with what inputs.
- Add an agent to the roster and every workflow can use it. Retire one, nothing else breaks.
02 · Level two · How it works
How the platform works.
The middle of the stack — what the capabilities above depend on. Instrumentation from the first call. Every output kept as a reusable asset. Multi-tenant by design, not by retrofit.
Live
02.1 · Capability
Telemetry
Full telemetry out of the box.
Full telemetry out of the box — no separate build required. Every agent call, every tool invocation, every human decision streams into a single pane, so cost, latency and quality are readable from day one.
What it means for you
- Cost per agent, per action, per workflow — visible as it happens, not month-end.
- Latency and quality tracked per model, so model choice is a data-led decision.
- No separate observability project needed to know what the platform is doing.
Live
02.2 · Capability
Reusable results
Every output is queryable and auditable.
Every workflow's output becomes a queryable, auditable asset. Answers don't vanish into a chat window — they land as first-class rows in tables the next agent can read, the next dashboard can chart, and any auditor can inspect.
What it means for you
- The answer to Monday's question is available for Tuesday's follow-up, without re-running the workflow.
- Downstream workflows compose on upstream outputs — the network effect grows with use.
- Every result is signed, timestamped and traceable to its inputs.
Live
02.3 · Capability
Multi-tenant
One platform, many clients, from day one.
Multi-tenant from the ground up — one platform, many clients. Tenancy is enforced at the control-plane level, not sprinkled through the code — so scale, isolation and audit are the same story, not three different ones.
What it means for you
- Regional deployments share the same product, so upgrades and improvements land everywhere at once.
- Tenants can be organisations, business units, or environments — the model is the same.
- Isolation is enforced at the database and orchestrator, not by convention.
03 · Level three · What it runs on
What the platform runs on.
The bottom of the stack — the choices we made once so you never have to. Any model. Any database. Open, client-owned tables. A single control plane that holds state and permissions.
Live
03.1 · Capability
Model & tool access
Any model, any database, no rebuild.
OpenRouter for any model, MCP tool sets against any database — swap either without a rebuild. Model choice is a decision per agent, not per tenant; connector choice is a decision per source, not per platform.
What it means for you
- A frontier model today, a locally-hosted model tomorrow — the agent above stays the same.
- New data sources reach the platform through typed MCP connectors, added in days.
- You are never locked to one vendor's model or one vendor's data stack.
Live
03.2 · Capability
Control plane
PostgreSQL holds state and permissions.
PostgreSQL as the control plane, so state and permissions live in one place. A boring, battle-tested database at the centre of the platform is what makes the rest of the choices work.
What it means for you
- One authoritative place for tenants, agents, workflows, permissions and telemetry.
- No exotic runtime to operate — Postgres skills you already have.
- Backup, replication and disaster recovery are solved problems here, not bespoke ones.
Live
03.3 · Capability
Iceberg
Open, client-owned tables underneath.
The open, client-owned table format underneath every result. Apache Iceberg means your data stays yours, in a format any modern engine can read, with time-travel and schema evolution built in.
What it means for you
- Every table an agent writes is a table you can query from Snowflake, Databricks, Spark, DuckDB, Trino — anything.
- You own the tables. Leaving mAIstro is a config change, not a migration.
- Schema and time-travel are first-class, so “what did we know on the 12th?” is a query, not a project.
04 · The promise · Governance
What makes mAIstro safe.
Three properties the platform holds — always, on every tier, on every deployment. If any of these breaks, the platform breaks. That is why governance is a first-class layer, not a policy document.
04.1 · Property
Trust
Answers you can take to the board.
Answers you can take to the board or a regulator without hedging. Every answer carries its evidence with it — inputs, agents used, tools called, decisions made — so review is a click, not a project.
What it means for you
- Every answer is defensible in front of an auditor without extra preparation.
- Confidence is visible: the platform says when it doesn't know, and shows what would raise the confidence.
- Sensitive actions require the right human at the right approval level.
04.2 · Property
Consistency
Same question, same answer, every time.
The same question returns the same answer — across teams, sites and time. Determinism is a design goal, not a happy accident. When two teams ask the same thing, they get the same answer or a documented reason they don't.
What it means for you
- Regional teams and central teams operate on the same numbers.
- Version, prompt and model changes are recorded — an answer today is comparable to an answer last week.
- No two dashboards show two different truths for the same question.
04.3 · Property
Integrity
Every figure traces to its source.
Every figure traces to its source; nothing silently adjusted. When a number changes, the platform says which upstream value moved and when. No orphaned adjustments, no silent overrides.
What it means for you
- Lineage is a live property of the platform, not a document that gets stale.
- Every change is signed, timestamped and attributable.
- Right-to-erasure and other data-rights obligations propagate through the ledger.
05 · The promise · Differentiators
What moves the number.
Three things mAIstro does that most agent platforms don't. The measures we're happy to be judged on — and the reasons finance and operations teams stay after the pilot.
05.1 · Differentiator
Optimisation
Improves the position, not just reports it.
Moves past reporting the position to improving it. A report tells you where you are; an agent tells you what to do next. mAIstro is built to propose the next action and, where you allow it, take that action.
What it means for you
- Every workflow ends with a recommendation and, where policy permits, an executed action.
- Human-in-the-loop thresholds are configurable — set them by action, role and amount.
- The measurable delta between the position with mAIstro and without is the KPI.
05.2 · Differentiator
Agnostic
Sits across existing clouds and tools.
Sits across existing sources, clouds and tools. No rip-and-replace. mAIstro is the layer that spans what you already have — data warehouses, ERPs, CRMs, ITSMs, identity — and turns them into a coordinated system.
What it means for you
- Existing investments continue to earn — mAIstro coordinates them, doesn't replace them.
- Cloud choice, region choice, model choice — all are yours, all can change over time.
- Adding a new source is a connector, not a project.
05.3 · Differentiator
Acceleration
Collapses question to decision.
Collapses the distance from question to decision. Time-to-market is the KPI. The measurable difference is not that answers are better — it is that they arrive in minutes instead of weeks, and that the next action follows.
What it means for you
- Median time from kick-off to a running workflow: two to three weeks.
- Cycles that ran monthly can run daily; cycles that ran daily can run continuously.
- ROI is designed in at scoping, not discovered at year-end.
06 · Service · Data assessment
Know what you have before you build.
The first of two services that wrap around the platform. Before the first agent runs, mAIstro maps the estate, scores the data, and leaves an evidence trail — so what you build next stands on solid ground.
06.1 · Service
Estate discovery
Maps every source, pipeline and owner.
Maps every source, pipeline and owner — a live picture of your data estate rather than a snapshot in a slide deck. Agents crawl what's connectable and interview owners of what isn't.
What it means for you
- You see the shape of the estate — sources, flows, gaps, orphans — in a week, not a quarter.
- The map stays live: as systems change, the picture updates.
- Owners and stewards are captured alongside systems, so accountability is visible.
06.2 · Service
Quality baseline
Scores accuracy, completeness and lineage.
Scores accuracy, completeness and lineage across the estate. Not a single “data quality score” — three separate readings, per source, that tell you what to trust and what to fix before you build on top of it.
What it means for you
- Every source gets three scores, not one, so priorities are legible.
- The baseline informs which use cases go live first — you don't ship a workflow on data that can't carry it.
- Improvement is measurable against the baseline, not against a memory of last quarter.
06.3 · Service
Evidence trail
Every check logged, dated and repeatable.
Every check logged, dated and repeatable. The assessment is not a report; it is a set of running checks. Re-run it any time — the trail shows what changed, when and why.
What it means for you
- Auditors can inspect the checks themselves, not just a document about them.
- Assessment becomes an operating rhythm, not a one-off exercise.
- The evidence trail becomes the foundation for the audit trail once agents go live.
07 · Service · Planning & modernisation
From assessed to running.
The second service. Once the estate is mapped, mAIstro designs the target architecture, sequences the migration and does the heavy lifting — so the move is measured in weeks, not years.
07.1 · Service
Target architecture
Open tables, one control plane.
Open tables, one control plane. The target is not a diagram — it's a working reference build of your estate on mAIstro, with the same three levels, the same governance, and the same differentiators as any other client.
What it means for you
- The target is opinionated — Iceberg tables, Postgres control plane, MCP connectors — so decisions are made once.
- Your data stays yours; the shape it lands in is open and portable.
- New use cases plug into the same target — nothing bespoke per project.
07.2 · Service
Sequenced roadmap
Phased migration, no big bang.
Phased migration, no big bang. The roadmap is ordered by ROI and dependency, not by convenience. Each phase delivers a running use case, not a milestone slide.
What it means for you
- Every phase ends with something in production — the platform earns as it lands.
- Dependencies are made visible so no phase is blocked by a hidden upstream.
- The plan is measured against realised ROI, not planned effort.
07.3 · Service
Delivery at pace
Agents do the migration heavy lifting.
Agents do the migration heavy lifting. Schema translations, data movement, pipeline rewrites, connector authoring — the parts that used to take teams take agents. Humans supervise, decide, approve.
What it means for you
- Time-to-first-workflow measured in weeks, not quarters.
- Your team's time is spent on decisions, not on hand-coded migrations.
- The knowledge transfer is embedded — your team runs the platform after handover.