Our pricing page has been telling you something wrong since the end of August. It badged Growth, Scale and Enterprise "Launching soon" — while we were already assigning those plans to customers and enforcing them in the product. The badge was on the wrong noun: the plans were live, the checkout was not.
This post is the correction, and the tour of what shipped alongside it.
The plans are real. What's launching soon is the checkout
Managed billing has been live and sales-led since 2026-08-31: our team assigns a plan, and the entitlement gates have honoured it from that same day. All four plans are available today.
> Updated 2026-09-06. This post originally said Free and Growth shared the $0–$10k band, and that what separated them was how many AWS accounts you had connected. That rule is gone. It sounded tidy and it was not: a single-account customer spending thousands a month sat on Free and received the whole product for nothing, while a customer spending a fraction of that across two accounts was asked to pay. Free is now decided by spend alone — under $2,000/month. Nothing about the free feature set changed, and no existing customer's price went up as a result of the rewording; the bands above are current.
"Spend" means one specific, checkable number: your AWS bill for the prior calendar month (BilledCost, after credits) — the same total your Refine dashboard shows. The bands are half-open, so exactly $10,000 lands in Scale and in exactly one band.
What is genuinely still in build is self-serve card checkout. There is no payment rail yet: nothing is purchasable in-app, and paid plans are set up by our team. So the honest version of the old badge is one sentence — every plan is available today, and paid plans are arranged in a short conversation rather than at a card form.
What a plan never gates
Worth saying plainly, because "pricing launched" reads to a lot of people as "a wall went up." It did not. The customer dashboard, cost analysis and the security summary are never gated. Ingest is never blocked and your data is never truncated.
The rule we hold ourselves to: a free tenant sees less of the answer, not less of their bill. A tool that hides your own cost data behind a paywall isn't a cost-optimization tool.
Asking for a plan without leaving the product
Until this month, the only way to ask to be billed was the same contact form a stranger uses — reached by navigating away from whatever locked control gave you the idea. Now a locked control opens a request dialog where you are. It writes one row and emails a human.
Two things it deliberately does not do. It does not grant anything: a request is a row in a queue, and you have exactly the entitlements you had a second earlier. And it does not promise a plan — the dialog says we'll confirm the right fit when we email you, because the plan the published bands offer you is not always the plan we should invoice, and that is a conversation, not a form field.
The dashboard loads what you're looking at, once
The performance work we wrote about in August is now a contract rather than a round of fixes. A visit does one data sweep. Changing month is a fold over rows already in hand, not another download. Nothing pops up unprompted — no toasts, no jumping month picker, no five-second "error" card on a healthy slow load. A request that genuinely hangs gets a real failure card with a Retry, and that card never dismisses itself.
The app also got one visual language while we were in there: one card, one notice, one empty state, one focus ring, and tabular numerals on every figure so columns of dollars line up. Loading skeletons are sized from the same constants the charts render at, so the placeholder and the thing it stands in for agree.
What a paid plan unlocks — and two things it doesn't
A paid plan is the same ten capabilities on Growth and on Scale; the plans differ by band, not by features. AWS Organizations and management-account sync. Unlimited AWS accounts. All resource recommendations. Step-by-step fix guides on findings — the exact AWS Console steps for that resource and region, plus the official AWS doc. Showback and scheduled reports. Bulk tag remediation, which generates a ready-to-run AWS CLI script or Terraform patch. Anomaly thresholds, routing and mutes. Slack and Microsoft Teams alerts. Full security findings and on-demand scans. Daily digests.
Two clarifications we'd rather make than let you discover. Refine holds read-only credentials and never writes to your AWS account — that is why remediation is a guide or a generated script you run yourself, and it is a boundary we chose, not a gap. And SSO and advanced RBAC are still coming soon: they are named as Enterprise differentiators, they are not shipped, and a live plan is not a live feature list. Alerts reach you by email, Slack and Microsoft Teams, and that is the complete set.
Where to go with this
Refine customers typically save 25–40% of their AWS spend, and it's built by an AWS Advanced Tier Services Partner. The full comparison, the band definitions and the FAQ are on the pricing page; the reasoning behind the four-plan shape is in the original pricing post, which we've annotated rather than quietly rewritten.
If you want Growth, Scale or Enterprise switched on, talk to us — we'll confirm the band from your prior-month bill and set it up. And if anything above still reads as unclear or unfair, tell us: this post exists because a badge went unchallenged for four days.