<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>FinOps on Nuvika Blog</title><link>https://www.nuvikatech.com/blog/tags/finops/</link><description>Recent content in FinOps on Nuvika Blog</description><generator>Hugo -- 0.152.2</generator><language>en-us</language><lastBuildDate>Thu, 07 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.nuvikatech.com/blog/tags/finops/index.xml" rel="self" type="application/rss+xml"/><item><title>FinOps Isn't About Cutting Cloud Spend. It's About Owning It.</title><link>https://www.nuvikatech.com/blog/posts/finops-mindset-shift/</link><pubDate>Thu, 07 May 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/finops-mindset-shift/</guid><description>The mindset shift from &amp;#39;reduce the bill&amp;#39; to &amp;#39;make every dollar intentional&amp;#39; — and what that means for engineering culture, vendor relationships, and how you build product.</description></item><item><title>How Much Are You Leaving on the Table? A FinOps Audit Checklist for Cloud Teams</title><link>https://www.nuvikatech.com/blog/posts/finops-audit-checklist/</link><pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/finops-audit-checklist/</guid><description>Five questions every CTO and cloud team should ask about SLA credits, cost anomalies, and billing accuracy — with specific things to look for in AWS, Azure, and GCP.</description></item><item><title>The 9 Commits That Completed Our Multi-Cloud SLA Claim Filing Module</title><link>https://www.nuvikatech.com/blog/posts/nine-commits-claim-filing/</link><pubDate>Sun, 03 May 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/nine-commits-claim-filing/</guid><description>A technical founder&amp;#39;s honest account of shipping a complex multi-provider feature: what we designed, what we got wrong in code review, and what we&amp;#39;d do differently.</description></item><item><title>920 Tests, 0 Failures: What AI Pair Programming Actually Looks Like in Production</title><link>https://www.nuvikatech.com/blog/posts/920-tests-ai-pair-programming/</link><pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/920-tests-ai-pair-programming/</guid><description>How we used Claude Code to implement, review, and verify a complete feature end-to-end — TDD, subagent-driven development, two-stage code review. What worked, what surprised us.</description></item><item><title>How We Built 433 Cloud Scan Rules Across 6 Provider Categories</title><link>https://www.nuvikatech.com/blog/posts/433-scan-rules-architecture/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/433-scan-rules-architecture/</guid><description>The rule engine architecture behind Fintropy&amp;#39;s cost optimisation scans — deterministic Tier 1 rules, AI-assisted Tier 2 rules, and a registry that auto-discovers both.</description></item><item><title>FOCUS 1.2: The Cloud Billing Standard Nobody Talks About (But Everyone Should Use)</title><link>https://www.nuvikatech.com/blog/posts/focus-1-2-billing-standard/</link><pubDate>Fri, 24 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/focus-1-2-billing-standard/</guid><description>Why Fintropy standardised all cloud billing records on FOCUS 1.2 internally — and why a common billing data standard is the unsexy foundation that makes multi-cloud FinOps possible.</description></item><item><title>What Happens When Your Auto-Filing System Fails at 2am</title><link>https://www.nuvikatech.com/blog/posts/error-handling-auto-file/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/error-handling-auto-file/</guid><description>The error handling design behind Fintropy&amp;#39;s auto-claim filing — why a filing failure must never break a breach resolution, and how we guarantee it.</description></item><item><title>AWS, Azure, and GCP All Speak Different Dialects. We Built a Translator.</title><link>https://www.nuvikatech.com/blog/posts/provider-vocabulary-normalisation/</link><pubDate>Fri, 17 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/provider-vocabulary-normalisation/</guid><description>How Fintropy normalises claim status vocabularies across three cloud providers — and why getting this wrong silently marks approved credits as denied.</description></item><item><title>The SLA Breach Lifecycle: From Cloud Incident to Credit Claim in 4 Steps</title><link>https://www.nuvikatech.com/blog/posts/sla-breach-lifecycle/</link><pubDate>Tue, 14 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/sla-breach-lifecycle/</guid><description>How Fintropy detects SLA breaches, quantifies their credit value, files claims automatically, and tracks approval — across AWS, Azure, and GCP.</description></item><item><title>We Built a FinOps Platform to Control Cloud Costs. We Deployed It Across Three Clouds.</title><link>https://www.nuvikatech.com/blog/posts/tri-cloud-deployment/</link><pubDate>Fri, 10 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/tri-cloud-deployment/</guid><description>The architecture behind Fintropy&amp;#39;s tri-cloud deployment: Dev on GCP, QA on Azure, Prod on AWS — and why each environment intentionally lives on a different cloud provider.</description></item><item><title>We Almost Chose Kubernetes. A Single Bug Changed Our Mind — And Created a New Problem.</title><link>https://www.nuvikatech.com/blog/posts/cloud-run-vs-kubernetes/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://www.nuvikatech.com/blog/posts/cloud-run-vs-kubernetes/</guid><description>How Fintropy switched from Kubernetes to Cloud Run, what we gained, and the cold-start SIGTERM problem nobody warned us about.</description></item></channel></rss>