Own it
What is running underneath, and which version.
The platform's own components on each host — with versions, state and recent restarts. When something behaves oddly, knowing whether a component was restarted an hour ago is usually the fastest route to the cause.
Services
- Per-host component list
- Version & drift visibility
- Restart history
- Dependency map
How it helps
What you get with Services
Versions visible
Which version is on which host, so a drift between two hosts is something you notice rather than deduce.
Restart history
Recent restarts and their reasons, which is often the whole explanation.
Dependencies mapped
What depends on what, so the consequences of taking a component down are known first.
Infrastructure control
The rest of Infrastructure control
For account admins: the servers, services, credentials, deployments, datacentres and tenant provisioning underneath it all.
Servers
The physical machines underneath, with their health and capacity.
Learn moreCredentials
Infrastructure secrets stored, rotated and access-logged in one place.
Learn moreDeployments
Every release, what it changed, and how to get back.
Learn moreDatacenters
Where your workloads physically sit, by name.
Learn moreTenant Provisioning
Stand up a new tenant through a reviewed workflow, not a runbook.
Learn moreSetup Wizard
Bring a new server into the estate with the checks built in.
Learn moreInfrastructure you can point at.
Start in minutes on dedicated capacity, or talk to us about private capacity and named datacentres. Every tier is the whole platform.
Every service, every tier Predictable egress No charge to open a ticket