Skip to content
Receipt-grade FinOps for teams that ship

Know what your cloud costs.And who it’s for.

Finn turns AWS, GCP, Azure, and OCI bills into cost intelligence your teams can act on. Allocate spend, compare clouds, model budgets, and keep every answer tied to its source.

Receipt-grade answersSource, window, metric, currency, and freshness stay attached.

Cross-cloud FOCUSAnalyze AWS, GCP, Azure, and OCI through one typed model.

AWS team allocationTurn tags into showback, chargeback, and frozen statements.

AWS budgets and alertsTrack plan, forecast, and anomalies from stored snapshots.

Illustration of Finn holding a glowing, receipt-like cloud cost report
FinnCloud Cost Expert
Finn · Cloud Cost Expert

Receipt before recommendation.

Finn is the skeptical quant on your platform team: calm about the bill, precise about the evidence, and allergic to savings claims that cannot be traced back to a source.

  • ObservedWhat the provider actually billed.
  • CalculatedWhat the receipt supports.
  • ModeledWhat could change, labeled as an estimate.
See how Finn follows every cloud dollar
AWS + demo attribution

Put a name on every dollar.

Finn's AWS snapshot and demo paths re-cut billing the way your business is organised — by team, product, environment, or customer — using the tags you already have. Whatever isn't tagged is called out as unattributed, never quietly averaged away.

Spend by team · month to date illustrative
TeamMonth to datevs lastUntagged
Platform$16,204+4%1.2%
Data$11,880+21%0.8%
ML$8,942−3%4.6%
Growth$2,584+2%0.0%
Unattributed$2,708+11%
AWS + demo showback and chargeback

Send the bill to the team that ran it up.

On AWS and demo snapshots, create the teams your business actually has, give each the cost scopes it owns, and Finn produces a monthly statement per team — attributed spend, plus whatever you charge or credit by hand, in one number a team lead can be held to. Issuing a statement freezes it: later re-syncs, ledger edits, and reorgs never rewrite a bill a team has already seen.

Statement · Data team illustrative
June 2026
Attributed spendobserved$11,880.14
Shared platform servicesdeclared+$1,200.00
Committed-use creditdeclared−$300.00
Total$12,780.14
Issued · frozen 1 Jul 2026. Re-syncs and reorgs can't rewrite it.
Reports + dashboards

One answer per question. One page per audience.

Save a provider-neutral Cost Report across AWS, GCP, Azure, and OCI with its scope, comparison, forecast, filters, drilldown, and receipts attached. Turn that answer into a dashboard brief for the team that owns the spend or the exec review. What finance opens is the same evidenced answer engineering can inspect.

Team = Data window last 30 days illustrative
monthly budget 7 days ago today
sourceAWS billing
windowlast 30 days
updated14m ago
completeno gaps in this window
Budgets and anomaly alerts

Hear about it while you can still act.

Turn a live Cost Explorer slice into a budget, import finance’s monthly plan, and roll teams into portfolios up to ten levels deep. Finn shows actual, accrued pace, forecast, and room left even when nothing has fired. Every completed sync then re-evaluates actual and forecast thresholds; alerts land by email or webhook with the receipt they fired on, so the person paged at 3am gets evidence, not a red dot.

Finn · anomaly alert email · webhook
NAT gateway · Data team
today$1,284
baseline$410/day
change+213%
  • 3.1σ above its own history
  • over the $250/day floor
  • over the +25% change bar
evaluated on refresh · settled days only
One workspace, two data paths

Connect what you already run.

Finn normalizes every provider into FOCUS analytics for cross-cloud questions. AWS also has a snapshot path for Cost Explorer, team allocation, budgets, and anomaly monitors. The capability boundary is explicit while those workflows expand.

AWS + modeled demo Operate and monitor

Overview, Cost Reports, Cost Explorer, classic dashboards, team allocation, budgets, and anomaly monitors.

AWS, GCP, Azure + OCI Analyze together

Provider-neutral Cost Reports and dashboards, comparisons, forecasts, filters, drilldowns, share links, and receipt-carrying exports.

Security and access

Built to pass your review.

Finn is a read-only observer of your billing data. Here is exactly what it can reach, who inside your company can see it, and where the guarantees stop.

No long-lived cloud keys

AWS uses a cross-account role you create, bound to that connection's external ID. GCP, Azure, and OCI use immutable billing-export generations. No Finn field accepts a cloud access key, and no provider path can modify your account.

Billing scope only

The AWS policy covers Cost Explorer reads; the other providers contribute billing rows through exports. Finn cannot see application data or change workloads — only read the cost evidence you connect.

SSO and shared workspaces

Sign in with your Zimac account. An org workspace shares connections and dashboards with every member, and access is re-checked on every request — remove someone from the org and their access ends immediately.

Numbers you can defend

Every figure carries its source, its window, and how fresh it is. Anything Finn derived — a forecast, a baseline, an impact estimate — is labelled as derived rather than presented as billing fact.

Pricing

Know your cloud costs. Without increasing them.

One hosted workspace gets the whole product for $49 a month, flat — not a percentage of the bill you’re trying to shrink. Track $5,000 or $5,000,000 of cloud spend without moving into a new tier, paying per seat, or booking a sales call.

The whole product
$49/ workspace / month

Month to month. No contract, spend percentage, seat fee, or feature ladder.

  • Unlimited tracked cloud spend and workspace members
  • Up to 16 AWS, GCP, Azure, and OCI sources
  • Cross-cloud Cost Reports, FOCUS dashboards, and exports
  • AWS Cost Explorer, team allocation, and statements
  • AWS budgets, anomaly monitors, email and webhook alerts
  • Read-only API and AI-agent access
Questions people actually ask

Before you connect anything.

Straight answers about setup, access, attribution, pricing, and who can see what.

How long does it take to see something useful?

Signing in takes a click. AWS uses the read-only role and policies Finn hands you; GCP, Azure, and OCI use a registered billing-export generation. The first AWS sync fills recent snapshot history, while an export lights up cross-cloud Analytics. A demo workspace works immediately with no cloud connected.

What access does Finn actually need?

Cost and usage evidence, and nothing else. For AWS, Finn shows the exact cross-account role policies and binds the role to a connection-specific external ID. GCP, Azure, and OCI register immutable billing-export metadata. No cloud access keys are entered or stored, and Finn has no provider write path.

Can I split spend by team without re-tagging everything?

For AWS and demo snapshots, yes — Finn discovers the tag keys already in use and you pick which ones to track. Whatever isn't tagged is reported as unattributed rather than silently spread across teams, showing where the tagging policy leaks.

Can we actually charge teams for what they use?

On AWS and demo snapshots, yes. Define teams, assign each the scopes it owns, and Finn attributes spend day by day. Add shared-service charges or credits, then issue a frozen monthly statement that a later re-sync or reorg cannot rewrite. Start with showback if your organisation is not ready to move money.

What exactly does $49 cover?

One hosted workspace, every shipped Finn feature, unlimited members, and unlimited tracked cloud spend. Finn does not charge a percentage of your bill or create a higher tier when your infrastructure grows. The service still applies the same published source, query-rate, scan, and retention safeguards to every workspace.

Who inside my company can see the spend?

Whoever you invite to the workspace. An org workspace shares connections and reports and dashboards with its members; a personal workspace is yours alone. Membership is checked on every request, so removing someone from the org ends their access right away. Note that a dashboard's scope filter is a convenience for readers, not a per-row permission boundary — everyone in a workspace can see that workspace's data.

Get started

Three minutes to your first cost report.

Sign in with Zimac, connect a cloud read-only or start with the demo workspace, and share the result with your team.