Pricing
Pricing anchored to cloud spend, not headcount
Flat monthly rate based on total annual cloud spend under management across all connected AWS accounts and GCP projects. No per-seat fees. No per-cloud-provider fees. 14-day free trial on Starter and Growth — no credit card required.
Choose your plan
Starter
$490
Billed monthly
Up to $500K/year cloud spend
- AWS CUR + GCP Billing Export attribution
- Team-level cost allocation with tag enrichment
- Zombie resource detection (EBS, EIP, LB, stopped instances)
- 7-day cost lookback
- Cost anomaly alerts via Slack
- Email support
Most Popular
Growth
$1,490
Billed monthly
Up to $2M/year cloud spend
- Everything in Starter
- Kubernetes namespace + pod cost allocation (EKS, GKE)
- Amortized RI and Savings Plan cost distribution
- Custom allocation hierarchies
- 30-day cost lookback
- PagerDuty anomaly routing
- Custom cost reports with CSV export
- Priority email support
Scale
$3,900
Billed monthly
Up to $10M/year cloud spend
- Everything in Growth
- AWS Organizations multi-account attribution
- GCP multi-project Billing Export aggregation
- CUD utilization analysis per team
- 90-day cost lookback
- REST API access for custom integrations
- Dedicated onboarding session
- SLA-backed support (4-hour response)
Compare plans
| Feature | Starter | Growth | Scale |
|---|---|---|---|
| Cloud spend supported | Up to $500K/yr | Up to $2M/yr | Up to $10M/yr |
| AWS CUR attribution | |||
| GCP Billing Export | |||
| Team-level cost allocation | |||
| Zombie resource detection | |||
| Cost lookback | 7 days | 30 days | 90 days |
| Kubernetes namespace attribution | — | ||
| Custom allocation hierarchies | — | ||
| PagerDuty integration | — | ||
| Multi-account AWS Organizations | — | — | |
| CSV export + API access | — | — | |
| Dedicated onboarding | — | — | |
| Support | Priority email | SLA-backed |
Frequently asked questions
We calculate your tier based on total annual cloud spend across all connected AWS accounts and GCP projects, normalized to a monthly rate from the trailing 3-month average. Amortized Reserved Instance and Savings Plan costs count toward your total. Credits and discounts applied by your cloud provider reduce the figure. We reconcile at the end of each billing month and adjust your tier if spend has changed substantially.
AWS Cost and Usage Reports are refreshed up to 3 times daily once AWS publishes the daily CUR file to your S3 bucket (typically within 24 hours of the billing day closing). GCP Billing Export to BigQuery is updated daily by Google. FinOpsVyn polls your BigQuery export dataset every 6 hours. Zombie resource detection runs on a daily scan cadence. Cost anomaly alerts compare against a 14-day rolling baseline and fire within hours of a spike exceeding your configured threshold.
FinOpsVyn discovers tag coverage gaps — it does not enforce tagging policies or block resource creation. Tag enforcement (e.g., using AWS Service Control Policies or GCP Organization Policies) is the responsibility of your platform team. FinOpsVyn surfaces the untagged spend and shows which teams and resource types have the lowest tag coverage, so you can prioritize where enforcement is worth the effort. For untagged resources, the attribution cascade uses Terraform state and CODEOWNERS to fill the gaps.
Terraform is fully supported on all plans — we read remote state from S3 backends, GCS backends, and Terraform Cloud workspaces. Pulumi support is on the roadmap; teams using Pulumi today can use the custom YAML ownership manifest as an interim fallback. CloudFormation stack tagging is supported via tag enrichment from CUR. FinOpsVyn does not read or modify Terraform plan files, state lock data, or provider credentials — only the read-only state JSON.
No DaemonSets and no agents deployed into your cluster. FinOpsVyn uses a read-only kubeconfig with ClusterRole access on pods, nodes, namespaces, and resource quota. We poll the Kubernetes metrics API on a 15-minute cadence to read CPU and memory requests per pod, then correlate with actual node costs from your CUR or GCP Billing Export to produce proportional cost allocations per namespace and workload. This approach works for EKS, GKE, and self-managed clusters. It is not a replacement for your platform engineering team's judgment on right-sizing — it surfaces the data so that judgment is informed.
Yes. Starter and Growth plans include a 14-day free trial with full attribution features. No credit card required. We onboard new trial accounts weekly and will reach out within 2 business days of your request.
AWS (via Cost and Usage Report) and GCP (via BigQuery Billing Export) are fully supported today. Azure Cost Management export ingestion is in beta — contact us if Azure is in your stack. Multi-account AWS Organizations setups are supported on Scale plan. Multi-project GCP billing aggregation is supported on Growth and Scale. A single FinOpsVyn account can connect both AWS and GCP simultaneously and show a unified cross-cloud cost view per team.
Yes. Month-to-month billing with 30 days notice to cancel. After cancellation, all your billing data stored in FinOpsVyn is deleted within 30 days. Read-only IAM roles and GCP service accounts you created for FinOpsVyn can be revoked immediately — we have no write access to revoke on our end.