This interactive snapshot helps you quickly assess whether your current cloud practices put you at risk of cost runaway—unexpected spend spikes or slow, compounding cost creep. In a few minutes, you’ll see your risk level, the biggest drivers of exposure, and practical actions to reduce risk and improve cost control. Your inputs stay in the browser. You can export or share the results to align engineering, platform, and finance teams on what to fix first.
Progress: 0 answered, 0 N/A, 16 remaining
Resources reliably include owner/team, app/service, environment, and cost-center tags/labels; enforcement prevents untagged spend.
Budgets exist at org/account/project and team levels; alerts route to the right owners with clear thresholds.
Cost data is accessible to teams and can be tied to deployments, scaling events, and feature launches.
Teams see their bill and are accountable for keeping it healthy; platform/shared spend is allocated transparently.
Unattached disks, idle load balancers, old snapshots, unused IPs, oversized non-prod, and abandoned sandboxes are pruned automatically.
Quotas/limits, approved instance families/sizes, and policy-as-code prevent ‘one click to $10k/day’ mistakes.
Ad-hoc console changes are minimized; drift is detected and reconciled to avoid resource sprawl.
Spikes trigger a known process: identify service, owner, blast radius, and mitigations quickly.
You regularly review utilization and adjust instance sizes, DB tiers, and container requests/limits.
Autoscaling cannot scale without bounds; scaling behavior is tested against failure/misconfig scenarios.
Retention policies, sampling, and log volume controls prevent observability bills from exploding.
Where workloads are steady, you use commitments and routinely verify you’re not wasting reserved capacity.
Batch jobs, CI, dev/test, and stateless services can opportunistically reduce cost with fallback strategies.
You track and optimize cross-zone/region traffic, CDN usage, caching, and unexpected outbound data movement.
Lifecycle rules remove old versions/snapshots and move cold data to cheaper tiers; backup retention is intentional.
When spend changes, you can identify ‘what changed, where, and who owns it’ quickly.
No foundational items detected (or not enough answers yet).
Get Unlimited PTO, 401(k), Health & Dental Insurance, and many more perks when you join our team.
Have questions? Our community is here to help. Learn more about our community
and Counting
We Are Proud to be an
International Employer
A practical primer on Kubernetes as a desired-state control system: what pods, deployments, services, ingress, config, secrets, autoscaling, namespaces, and cluster operations actually do, and what they do not do.
A practical, workflow-first guide to Docker and Kubernetes that explains images, registries, runtimes, deployment automation, and the boundaries that keep container systems understandable and secure.
A cloud-native development operating model turns delivery into a paved road for the common case—automated, observable, and governed—while keeping exceptions explicit and reviewable.
Platform engineering vs DevOps isn’t either/or. Use the right operating model for the bottleneck you actually have—ownership and feedback loops for DevOps, and self-service to reduce delivery toil for platform engineering.