mission-finops --about
We investigate AWS cost movement and improve the engineering behind the bill.
Independent engineering practice. Built on hands-on infrastructure experience across networks, firewalls, data centres, application migrations, DDoS mitigation, and scaling systems under pressure. Then nearly seven years at AWS advising enterprise customers across banking, telecom, government, and gaming. Now helping engineering teams investigate and improve the systems behind their cloud bill.
If the AWS bill goes up, we help find out what changed.
If the system is wasteful, we work with engineers to improve it.
If finance and engineering are speaking past each other, we help both sides work from the same evidence.
start-here
Most engagements begin with an AWS Cost Investigation. One material cost question, investigated against your billing data and your architecture. You get the evidence, the confidence limits, the likely owner, and the next actions. Fixed fee, roughly two weeks.
Read-only AWS access. Published IAM policy.
Runs locally. Customer data is not sent to Mission FinOps or a third-party SaaS.
None. No phone-home. No usage tracking.
Stays with you. No SaaS. No mandatory upload.
Open source. Inspect before you trust.
We were founded in Mission, BC, on Stó:lō land. The Stó:lō have a word, tómiyeqw, meaning both great-great-great-great-grandparent and great-great-great-great-grandchild. One word, seven generations back and seven forward, with the responsibility resting on whoever is standing in the middle.
We are not going to pretend cloud infrastructure carries that weight. But it is a good thing to have in mind when someone signs a three-year commitment.
mission-finops --what
Cloud cost is the result of engineering decisions.
A bill is where the number appears. The cause lives somewhere else: architecture, usage, deployment choices, ownership, commitments, data movement, or a system that no longer fits the job.
- bill-changed
We investigate the movement and connect it to the workload, service, account, or business event that caused it.
- recs-pile-up
We help engineers decide what is worth changing, what is safe to leave, and what creates a better system.
- finops-gap
We help build shared language, evidence, queries, runbooks, and habits that engineers will actually use.
- data-control
We work local-first and read-only. No sensitive business context leaves your environment.
mission-finops --how
We work with your builders, not around them.
We sit with the people who know the system, test the cost story against technical reality, and help turn the answer into better engineering.
Some of the useful work becomes open source. Some stays inside your company. Either way, your team owns more of the capability when we leave.
kulshan --version
Kulshan is the evidence engine behind the work.
Free, open-source AWS cost investigation CLI. Runs locally with read-only access and produces evidence-backed reports from the customer's own environment.v0.5.0APACHE-2.0
EC2 spend increase +38% m/m
14 idle EBS volumes ($312/mo)
NAT Gateway anomaly (z-score 2.4)
Savings Plan coverage 47% below baseline
$ kulshan report --packs cost --days 90 --format json -y kulshan 0.5.0 | cost pack | 90 days | 3 regions ⬢ CUR/Data Export found ───────────────────────────────────────────── human_review_required: yes report written → ./kulshan-report.json
Not a subscription. Not a dashboard. Proof of the way we work: keep data controlled, make the method inspectable, give the builder something useful.
whoami
Mission FinOps came from engineering, not finance.
Mission FinOps is led by Yuvdeep Singh, a former AWS Technical Account Manager and Solutions Architect with nearly seven years supporting large enterprise customers across telecom, banking, gaming, and government in North America.
Before AWS: networks, firewalls, data centres, architecture leadership across complex on-prem environments.
That path is why Mission FinOps does not treat cost as a finance-only exercise. We understand the physical system, the cloud architecture, the trade-off, and the meeting where somebody has to explain the number.
mission-finops --engage
Bring us the messy question.
"The bill moved and nobody agrees why" is enough. So is "we know there is waste but the engineering team does not trust the recommendations."
We scope engagements after a fit conversation. See how the work is shaped.
calendly → book