Know what runs. See what changed.

Estate

• Inventory, derived health and the permanent status history available now
• The Dashboard: what needs someone now, ranked, each item linked to the page that explains it, then the estate by cloud and category, collection, spend against forecast, provisioning, recent changes and the hottest resources — the first page after sign-in available now
• Alerts, Slack and webhook notifications, and a public status page without identifiers — the front door for a visitor with no session available now
• Microsoft Teams, PagerDuty and email channels, each tested against a stand-in, email also against a real mail server; delivery to a live PagerDuty service and through a live mail relay is proven by the operator, with a step in the operator's manual available now
• Acknowledgeable alerts: a member acknowledges with a required note; the alert leaves the list until the resource changes again, and the acknowledgement is on the timeline available now
• Tag-defined application groups and declared apps, and freshness by each module's cadence available now
• Configuration diffs between snapshots on every resource's page, sensitive fields suppressed available now
• The change feed: configuration diffs, status transitions, acknowledgements, provisioning outcomes, cost anomalies and budget thresholds in one timeline per resource, account, app and team, ordered by the event's own time, with markers the customer's own systems post under a marker credential available now
• Ownership: one resolver deciding every resource's owning team from overrides, provenance, tags, the account and its relationships, with confidence and evidence, on every page that names an owner available now
• Impact and the investigator: one change and what moved around it — status, performance and settled cost on the resource and its neighbours — and, for a symptom, the changes before it ranked by time, distance and kind, each a candidate and never called a cause available now
• Tag policy: the tag keys a resource must carry and the values each admits, who complies with the money beside each answer, and at creation the agent stamps the team key, a request the policy cannot satisfy refused before it exists available now
• Findings: what needs fixing, grouped and prioritised, each priority showing its parts and its evidence available now
• Change alerts: a subscription to configuration changes that match a small predicate, judged as each read arrives, for a team or a declared app available now
• Relationships: a resource's neighbours — what contains it, what runs on it, what fronts and guards it, what provisioned it, the apps it belongs to, the team that owns it — each with evidence and confidence, drawn on its page available now
• Performance: latency, errors and saturation from CloudWatch with statistics, interactive charts and topology diagrams; EKS in depth, from the control plane to each pod available now
• Performance in depth: maxima, p95 and p99, a 30-day window read from an hourly rollup, and the hottest resources per signal with their pressure and a sparkline available now
• Performance for Google Cloud projects, from Cloud Monitoring: Compute Engine instances, Cloud SQL instances, Cloud Storage buckets, Application Load Balancers' forwarding rules, Cloud Run services, Pub/Sub topics and subscriptions, with the same statistics, windows and charts available now
• Performance for Azure subscriptions, from Azure Monitor: virtual machines, PostgreSQL flexible servers, SQL databases, storage accounts, App Service apps and AKS clusters, with the same statistics, windows and charts available now
• The inventory read every ten minutes, and the EC2 instances that start and stop between two reads recorded from EC2's own state-change events, with each run's start, end and lifetime in Changes available now
• Who made a configuration change: the CloudTrail events that may be it — principal, call and time, each a candidate and none chosen — on the change in Changes and in the investigator's evidence, for an AWS account whose administrator turns CloudTrail attribution on, within CloudTrail's 90 days available now
• Accounts: every connected AWS account, Google Cloud project and Azure subscription as an overview — what it holds by status and region, the state of its collection, the worst and stalest collector and when it was last read successfully — for any signed-in member available now
• Google Cloud projects: Compute Engine instances, GKE clusters, Cloud SQL instances, Cloud Storage buckets, VPC networks and subnets, Cloud Run services, Pub/Sub topics and subscriptions, BigQuery datasets, service accounts, Firebase apps and Cloud Functions, read through workload identity federation with a metadata-only custom role, every request field-masked available now
• Cloud Functions read from the Functions API's masked listing: every function under its own name whether or not it has run, with its state and labels, gone when the listing stops naming it available now
• Azure subscriptions: virtual machines, AKS clusters, SQL databases, PostgreSQL flexible servers, storage accounts, virtual networks and App Service apps, read by an app with no secret through federation and a custom role with no data action, connected from Admin → Accounts; every collector, and the role's refusal of content reads, verified against a live test subscription available now