Ji-woo Han
Account Executive
Built where finance and engineering share a subway line
NimbusLedger started after a midmarket retailer’s FinOps lead asked why their “savings program” could not show margin impact the way inventory turns already did. We still anchor every roadmap to that question, even as the product surface grew from Pulse alerts into multi-SKU governance.
Field org chart
Reporting lines show who answers first when a deployment goes sideways versus when a board deck needs a footnote—not who wins arguments on Slack.
Mika Lee
Solutions Consultant
Rae Jung
FinOps Analyst
Hana Seo
Cloud Economist
Noah Han
Customer Success Manager
Leo Park
Implementation Specialist
Sora Kim
Support Lead
Operating principles
- Evidence over theater: every public claim ties to a reproducible export path inside the product.
- Accountability routing: savings ideas carry owners, not anonymous “ops” comments.
- Regional honesty: Korean consumer and enterprise rules shape our defaults, even when the UI ships in English.
What members say about the plans
“Harbor Chargeback Forge finally let our platform tax stop double-counting the observability stack—still noisy when finance disagrees with coefficients, but the noise is logged now.”
Also heard from Min in Seoul: “Weekly digest is the only mail I open before coffee.”
“Stride cards that cite the metric window kept our SRE council from rubber-stamping downsizing we would have regretted.”
“Covenant scenarios made our CFO workshop shorter; still wish the UI exposed FX knobs sooner.”
“Lattice Kubernetes Meter highlighted daemonset amortization we were quietly eating—uncomfortable meeting, useful outcome.”
“Northwind FinOps Flow did not remove politics, but it did timestamp when procurement stalled versus engineering.”