Modules
Every module in the product, organised into the fourteen navigation sections the application itself uses.
This is the heart of the documentation: 48 modules across 14 sections, each documented against the same template so any two can be compared directly.
If you are not technical, read this first
You do not need to read all 48. Each module page opens with what it is, who it is for, and closes with why it matters — those three parts are written in plain language.
The section headed How it works is the mechanism, and it is safe to skip.
The fourteen sections
| Section | Modules | What it is for |
|---|---|---|
| AI & Automation | 3 | Apex, the agent workforce, and unattended automation |
| Insights | 4 | Where the estate stands — overview, executive view, intelligence, reports |
| Optimization | 4 | Waste, the queue of work for it, lifecycle, and parking |
| Workloads | 4 | The systems that spend — AI infrastructure, databases, APIs, Kubernetes |
| Engineering | 3 | Cost at the point of change — CI/CD, deployment and migration, pull requests |
| Cost & Spend | 5 | Where the money goes — billing, cost centres, showback, unit economics, allocation |
| Analyze | 1 | Vendor spend that never appears on a cloud bill |
| Planning | 4 | What happens next — forecasting, scenarios, benchmarks, maturity |
| Govern | 5 | Controls — rules, gates, ownership, evidence, tagging |
| Security | 3 | Estate posture — inventory, security-cost posture, compliance |
| Admin | 4 | Tenancy — organisation, workspaces, analytics, identity |
| Connections | 3 | What the platform may read — cloud accounts, integrations, AI providers |
| Account | 2 | Commercial — plan, entitlements, credits, profile |
| Help & Updates | 3 | Assistance — support tickets, error history, documentation |
You are not locked into these sections
The sidebar layout editor lets each user regroup modules into anywhere from 3 to 15 custom groups, saved per person. The sections above are the defaults.
In a product this broad, a 48-module sidebar serves nobody — letting each person shape it to their own job is what keeps it navigable. Configured in Settings.
How the sections connect
The product is deliberately a connected system, not a set of independent dashboards. Every module page ends with a Connects to section naming what it feeds and what it depends on.
The module template
Every module page answers the same questions in the same order:
| Section | What it answers | Written for |
|---|---|---|
| At a glance | Route, section, permission | Administrators |
| What it is | A plain-language definition | Everyone |
| Who it is for | The roles that live here day to day | Everyone |
| How it works | The actual mechanism | Technical readers — safe to skip |
| Features | The concrete capability list | Everyone |
| How to use it | A numbered operating procedure | Practitioners |
| Why it matters | The business outcome | Everyone |
| Connects to | What it feeds and depends on | Everyone |
Start here
Apex
Ask questions in plain English. The lowest-friction entry point in the product — start here if you would rather ask than learn a dashboard.
Overview
The page most people open first each day: what you are spending and whether the number can be trusted.
Opportunity Queue
Where every detection lands as a costed, scored finding — the working list for saving money.
Complete module index
All 48 modules, routes, sections, and permissions in one table.