// the take
Ice is Netflix's old internal tool for visualizing AWS cost and usage, originally released around 2013-2014. It's a three-part Grails app (processor, reader, UI) that ingests AWS detailed billing files and renders interactive cost/usage dashboards, with support for grouping resources into application groups for per-team cost accountability. Aimed at infra/finance teams doing FinOps work at a company with enough AWS spend to care about reservation utilization and cross-account billing.
The processor/reader split lets you scale billing-file ingestion separately from the query/dashboard layer, and both can run on different instances. Cross-account IAM role support for reading billing data from a separate payer account is a real feature most DIY cost tools skip. The reservation view amortizes one-time RI purchases over time so month-to-month cost comparisons aren't skewed by upfront payments, and it factors in on-demand vs. reserved vs. unused RI cost breakdowns by instance type/account/AZ.
It's built on Grails 2.4.4, a framework version from 2014 that's long past EOL — standing this up today means fighting an old JVM/Groovy toolchain, not just deploying a jar. More fundamentally, it depends on AWS's legacy 'detailed billing reports' CSV format, which AWS deprecated in favor of Cost and Usage Reports (CUR) years ago; this likely doesn't ingest data from any AWS account provisioned in the last several years without serious rework of BillingFileProcessor. Several of the more useful features (resource/tag-based grouping, custom reservation pricing, weekly email reports) require writing and subclassing Java service interfaces yourself — there's no working implementation out of the box for anything beyond the basic account/region/service breakdown. No commits since 2022, so compatibility fixes for newer AWS billing formats aren't coming from upstream.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →