One control plane for three clouds
A single operational surface across AWS, GCP and Azure, with the access controls and onboarding to roll it out across a whole organisation.
Three consoles, three logins, three mental models. Nobody can answer what the whole estate costs or whether it is healthy without stitching screenshots together.
Unified multi-cloud dashboard
One view across AWS, GCP and Azure: spend, resource health and savings signals side by side instead of three consoles.
Every connected AWS, GCP and Azure account rolls up into one view, so spend, resource health and savings signals sit next to each other instead of behind three separate logins. The point is a single number you can trust for the whole estate, and one place to notice when it moves.
- Total and per-provider spend in a single roll-up
- Resource health and savings signals on the same screen
- No context switching between provider consoles
Per-account dashboards
Dedicated live dashboards for each AWS, GCP and Azure account.
Aggregate views hide the account that is actually causing the problem, so every connected account also gets its own live dashboard. Drill from the estate-wide number into the specific account, then into the resources inside it.
- A dedicated dashboard per AWS, GCP and Azure account
- Live data rather than a nightly export
- Drill-down path from estate roll-up to single resource
Guided account onboarding
Connect AWS via CloudFormation IAM role, GCP via service account, Azure via Service Principal with a generated PowerShell script.
Connecting a cloud account is the step where most platform rollouts stall, so each provider gets a guided path with the artefact it expects. AWS uses a CloudFormation stack to create the IAM role, GCP uses a service account, and Azure uses a Service Principal set up by a generated PowerShell script.
- AWS: CloudFormation template creates the IAM role
- GCP: service account credentials
- Azure: Service Principal via a generated PowerShell script
Permission-gap detection
When a restricted IAM policy blocks a data source, the UI names the missing permission instead of showing an empty chart.
Least-privilege policies and full visibility pull in opposite directions, and the usual result is a chart that renders empty with no explanation. Instead of failing silently, the UI names the exact permission the data source needs so whoever owns the policy can act on it.
- Names the missing IAM permission, not just "no data"
- Works per data source, so partial access still shows partial data
- Turns a support ticket into a self-serve fix
Command palette
Cmd+K jump-to-anything across accounts, resources and pages.
A platform this wide gets slow to navigate by clicking. Cmd+K opens a jump-to-anything palette that searches across accounts, resources and pages, so getting to a specific volume or dashboard is a few keystrokes rather than a hunt through menus.
- Cmd+K from anywhere in the product
- Searches accounts, resources and pages together
- Keyboard-first navigation for daily operators
Role-based access and tab entitlements
Per-user visibility down to the individual tab, so finance, engineering and support each see only their surface.
Finance, engineering and support each need a different slice of the same platform, and giving everyone everything is how rollouts get blocked by a security review. Entitlements go down to the individual tab, so each role sees only its own surface.
- Per-user visibility controlled at tab level
- Separate surfaces for finance, engineering and support
- Least-privilege access without running separate tools
Platform, answered.
AWS, GCP and Azure. Each provider has a guided onboarding path: a CloudFormation stack creates the IAM role on AWS, GCP uses a service account, and Azure uses a Service Principal configured by a generated PowerShell script.
No. XamOps works with restricted policies, and when a policy blocks a particular data source the interface names the specific missing permission instead of rendering an empty chart. You can start narrow and widen access only where you want the extra visibility.
Yes. Role-based access controls visibility down to the individual tab, so finance, engineering and support each see only the surface relevant to them.
A Cmd+K command palette jumps to anything across accounts, resources and pages, so daily operators do not need to click through menus.
Platform is one module of 8.
Ready to automate platform?
30-minute walkthrough. We connect to a sandbox and show this module running against real infrastructure.