Our story
Built by engineers who lived the problem
Founded in 2022 in San Francisco. The founding team built platform infrastructure at fast-growing companies, watched AWS bills cross seven figures, and saw firsthand that the cloud provider billing console stops being useful the moment more than one team touches the same account.
The problem we couldn't ignore
In 2020, Daniel Choi was leading platform engineering at a B2B SaaS company in San Francisco when the AWS bill crossed $2M for the first time. Finance sent around a cost allocation spreadsheet. It showed spend by service — EC2, RDS, data transfer — but nothing by team. Nobody could explain the $340K RDS line item or point to which squad's workload drove it.
The answer was always a month-end Athena query that a finance analyst ran against the Cost and Usage Report, then manually reconciled against a list of account tags that were six months out of date. By the time the attribution report landed in engineering, it was too late to act on anything in it.
Daniel spent six months building internal tooling: a pipeline that read CUR line items, enriched them with Terraform state to recover ownership for untagged resources, and pushed squad-level cost digests to Slack every Tuesday. It worked. Engineers started treating cloud cost as a first-class metric alongside latency and error rate.
In 2022, he left to build FinOpsVyn — to make that attribution layer available to every team managing meaningful cloud spend, without requiring them to build it from scratch. FinOpsVyn is that internal tool, productized, maintained, and extended to cover AWS, GCP, and Kubernetes in a single attribution model.
Our mission
"Make cloud cost accountability accessible to every engineering team managing meaningful spend — not just orgs with a dedicated FinOps analyst."
The team
Small team, all operators
No corporate org chart padding. Four people who have all been on the other side of the cloud billing problem.
Daniel Choi
CEO & Co-Founder
Former platform engineering lead at a B2B SaaS company in San Francisco. Spent 2017–2022 building internal cost attribution tooling on top of AWS CUR and Terraform state. Founded FinOpsVyn in 2022 to productize that layer for teams who can't afford to build it themselves.
Priya Sundaram
Head of Product
Previously built infrastructure observability tooling focused on cost and performance correlation. Joined FinOpsVyn in 2022 to design the attribution model's role-scoped views — making CUR-derived data readable by both platform engineers and finance teams without translation.
Marcus Riley
Platform Engineer
Kubernetes and AWS specialist who built EKS cost allocation tooling before joining FinOpsVyn. Owns the billing ingestion pipeline, the CUR-to-ownership join layer, and the read-only kubeconfig cluster metrics collection. Zero agents in production clusters is a hard constraint he enforces.
Lin Wei
Data Engineer
Owns the cost normalization layer: mapping AWS CUR line items and GCP Billing Export rows to a unified attribution schema that handles amortized Reserved Instance costs, Savings Plan distributions, multi-account consolidated billing, and multi-project GCP aggregation in a single model.
How we work
Three principles we don't compromise on
01
Attribution over approximation
Proportional allocation with a single blended rate per account is easy to compute and impossible to act on. We do the harder work: CUR line-item attribution enriched by Terraform state and CODEOWNERS, so every dollar traces to a specific team and service — not an estimated share of a bucket. Amortized Reserved Instance costs are distributed by the teams that actually consume the capacity, not left as an unallocated line item for finance to wrestle with.
02
Engineers read the data, engineers own the cost
Attribution data locked in a finance dashboard or a quarterly FinOps report changes nothing. Cost accountability reaches the FinOps Foundation "Run" maturity level only when the engineers who deploy infrastructure can see the cost of what they build — in Slack, at their sprint cadence, before the bill closes. FinOpsVyn is built to put that data in front of the person who can act on it, not the person who needs to report on it.
03
Detect before the bill closes
A month-end cost review is a postmortem. By the time the anomaly appears on the bill, the team responsible has already moved on. FinOpsVyn runs daily zombie scans and continuous anomaly detection against a rolling 14-day cost baseline per team — so a misconfigured EBS snapshot policy or a forgotten load balancer surfaces in hours, not weeks. The goal is zero bill surprises for every team we serve.