<?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>How Fintropy Works on Nuvika Blog</title><link>https://www.nuvikatech.com/blog/categories/how-fintropy-works/</link><description>Recent content in How Fintropy Works on Nuvika Blog</description><generator>Hugo -- 0.152.2</generator><language>en-us</language><lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.nuvikatech.com/blog/categories/how-fintropy-works/index.xml" rel="self" type="application/rss+xml"/><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></channel></rss>