Accounts discovered, not declared
Refine reads the linked accounts out of the payer export itself. Nothing to enumerate up front, and an account your team opens next month appears on the next sync without anyone telling us.
Product · MSP-ready · AWS Advanced Tier Services Partner
One pane for every AWS account you manage — yours or your customers’
Connect the management account once and every linked account is discovered from the export itself. Customer hierarchy, per-customer reports, and role-based notification routing on top.
customer hierarchyMSP-ready · per-customer reports
38
accounts
$214k/mo
monitored
1
pane of glass
Connect the management account once
Growth and up
Point Refine at one AWS Organizations payer export and it finds the linked accounts itself. There is no list to maintain and no connection to add per account — the accounts come out of the billing data, so an account added in AWS this week is simply there next sync.
Counted once, even when connected twice
Connect the payer and a linked account separately and Refine still totals that account once. The payer’s claim wins — it is the payer’s own data, and it carries the commitment allocation a linked account’s export cannot see.
Losing the cost claim never stops the scan
A connection superseded for cost stays in play for everything else. An account you are still paying for does not quietly drop out of security scanning because a payer export arrived.
Organization sync is what a paid plan is for. The Free plan covers one standalone AWS account; a payer export, and additional standalone connections, come with Growth and up. See what each plan costs.
Three-Tier Customer Hierarchy
Org → Customer → Account. Data, recommendations, and notifications are isolated to the customer they belong to. Aggregate views roll up at the org level.
Org
Acme MSP
Customer
Customer A
E-commerce
acme-shop-prod
prodacme-shop-staging
stagingCustomer
Customer B
FinTech
fin-payments-prod
prodfin-data-prod
prodfin-sandbox
devCustomer
Customer C
Healthcare
hc-platform-prod
prodhc-platform-dev
devNo per-seat and no per-account fee — plans are priced on your AWS spend band, so growing the estate does not grow the bill for watching it.
One Switcher - The Whole Fleet.
Switch context from the header. Dashboards, recommendations, and reports re-scope instantly to the customer you select. Org-level rollup view at the top for cross-customer health.
- Fuzzy search across customer names + account IDs
- Keyboard shortcut: ⌘K to jump
- Recent customers pinned to the top
- Bookmark filtered views per customer
Switch customer
- Acme MSP — Org
- Customer AE-commerce · 2 accounts
- Customer BFinTech · 3 accounts
- Customer CHealthcare · 2 accounts
- Customer DSaaS · 4 accounts
- Customer EAdTech · 1 account
- Customer FMedia · 2 accounts
- Customer GEdTech · 1 account
- Customer HLogistics · 5 accounts
- + 4 more
Right Signal, Right Inbox
Cost alerts to FinOps. Security findings to SecOps. On-call gets anomalies. Per customer, per severity, configurable from Settings.
| Signal | Recipient role | Example address |
|---|---|---|
| Cost spike | FinOps mailing list | finops@customer-a.example |
| Anomaly (high severity) | On-call rotation | oncall@customer-a.example |
| Security finding (critical) | SecOps team | secops@customer-a.example |
| Weekly cost report | Customer's primary contact | cfo@customer-a.example |
Alerts deliver by email, Slack, and Microsoft Teams — the same severity-aware routing on every channel.
Per-Customer Reports
Each customer sees only their own data. Schedule a recurring report once and customers receive their own version forever.
Strict Data Isolation
Customer A never sees Customer B's spend, findings, or anomalies. Org-level rollups only contain customer aggregates the user has access to.
Schedulable Cadence
Daily, weekly, or monthly per customer. Email scheduling lives in Settings → Reports.
Audit Log Per Recipient
See exactly which customer received which report, when. Useful for SLA evidence and customer onboarding.
White-Label / Co-Branded Reports
On roadmapOne caveat: customer-branded reports and a co-branded portal are not live today. They are on the roadmap. For now, reports carry the Refine brand. If white-labeling is a hard requirement for your partnership conversation, talk to us — we prioritize based on partner demand.
Frequently Asked Questions
- No. Refine never charges per account, per customer or per seat — plans are banded on your prior-month AWS spend, so connecting another account does not change what you pay. What the plan decides is scope: Free covers one standalone AWS account, and an AWS Organizations management-account export plus additional standalone connections come with Growth and up.
Become a Refine MSP partner
Start on Free. Customer-hierarchy-aware. Co-marketing kit included. White-label on the roadmap.
Refine is built and supported by HabileLabs, an AWS Advanced Tier Services Partner.