Cloud
How We Built 433 Cloud Scan Rules Across 6 Provider Categories
The rule engine architecture behind Fintropy's cost optimisation scans - deterministic Tier 1 rules, AI-assisted Tier 2 rules, and a registry that auto-discovers both.
Tag
All Nuvika Blog posts tagged “GCP”.
Cloud
The rule engine architecture behind Fintropy's cost optimisation scans - deterministic Tier 1 rules, AI-assisted Tier 2 rules, and a registry that auto-discovers both.
AWS
How Fintropy normalises claim status vocabularies across three cloud providers - and why getting this wrong silently marks approved credits as denied.
SLA
How Fintropy detects SLA breaches, quantifies their credit value, files claims automatically, and tracks approval - across AWS, Azure, and GCP.
Multi-Cloud
The architecture behind Fintropy's tri-cloud deployment: Dev on GCP, QA on Azure, Prod on AWS - and why each environment intentionally lives on a different cloud provider.
Cloud-Architecture
How Fintropy switched from Kubernetes to Cloud Run, what we gained, and the cold-start SIGTERM problem nobody warned us about.
SLA
When AWS, Azure, or GCP go down, you're still paying for infrastructure that didn't serve a single request. 85% of affected companies never file SLA claims. Here's how the other 15% recover the credits.