Customer Story · Public Sector
Cloud optimization that never leaves the tenant, for a multi-billion-dollar Québec institutional fund
A Québec institutional investment fund with several billion dollars under management and ~300 employees, running its Azure estate under strict data-residency requirements.
Regulated institutional fund Microsoft Azure 100% in-tenant deployment
Why public sector
Data residency isn't a preference here: it's the constraint everything else is designed around.
Public-sector and other regulated organizations face the same cloud waste every private company does, plus a hard requirement most SaaS optimization tools can't clear: data almost never leaves the tenant, and governance frameworks like Québec's Law 25 or OSFI-style oversight aren't policy exceptions to negotiate, they're satisfied by architecture or not at all. Jetscale runs as a dedicated, sovereign instance deployed inside the customer's own infrastructure. Every discovery, analysis, and report stays in-tenant. The case below is drawn from a large regulated institutional fund managed under exactly those constraints; the same sovereign-deployment model applies directly to government agencies, crown corporations, universities, and other public institutions with equivalent data-residency requirements.
Key metrics
The numbers at a glance.
The challenge
A hard residency constraint, and a cost function that never got built.
As a regulated financial institution, the fund could not send infrastructure or billing data to a third-party SaaS platform. Data residency was a hard constraint, not a preference. Meanwhile its Azure estate (100+ VMs, nearly 300 managed disks, and a storage-heavy footprint) had grown without a dedicated cost function, and non-production environments ran around the clock.
What Jetscale AI did
Architecture satisfies the compliance requirement, not a policy exception.
Deployed a dedicated sovereign Jetscale AI instance: all discovery, analysis, and reporting run inside infrastructure under the customer's control; nothing leaves the tenant. Residency and Law 25/OSFI-style governance requirements satisfied by architecture, not policy exceptions.
Full discovery across production, staging, and development subscriptions with daily cost ingestion at billing-line granularity.
Delivered a prioritized optimization roadmap plus a dedicated reserved-instance / savings-plan analysis for the VM estate.
Continuous governance monitoring: configuration gaps and anomaly detection on daily spend (including catching a one-day cost spike the team hadn't seen).
Results overview
A costed, governed estate (without a single byte leaving the tenant).
Results in details
What the fund's governance and finance teams got out of it.
List-price savings from resource optimization across 411 recommendations, plus $30–47K/yr from commitment pricing on the staging/dev VM estate.
Storage identified as the dominant waste source (2.3 managed disks per VM; hundreds of disk and storage-account actions), invisible in the standard Azure bill view.
Non-production running 24/7 flagged at ~14% of total spend: a direct scheduling opportunity.
~5 tonnes CO2e/yr of estimated emissions-reduction potential.
Details anonymized at the customer's request. Figures from the delivered assessment and live platform telemetry, 2026.
More stories
Read another industry.
Finance & Insurance
A $1M+/yr costed view of a $7.5M PE-owned Azure estate across 36 subscriptions.
Read the story →Software and AI
896 savings actions across 25 cloud accounts, in under three weeks, fully read-only.
Read the story →All customer stories
Back to the overview of all three engagements, side by side.
See all stories →Get started
See what Jetscale finds in your estate.
Read-only or fully sovereign, in-tenant deployment. Invoiced only when savings land.