Skip to content
All stories
EnergyOn-prem

Ironvale met a data residency requirement without a second codebase

A regulator required customer data to stay in-region.

Illustrative example

Ironvale is a composite example, not a named customer. The situation and the way it was solved are drawn from what teams actually bring to us; the company itself is invented. Real customer stories are published only with the customer’s permission and their own name on them.

per project
region choice
1
codebase
0
deployment forks

The situation

The obvious answer was a separate deployment, with everything that implies for releases and on-call.

What they did

Region is chosen per project at creation time, so the same application code serves both without branching.

What changed

One codebase, one release process, two regions.

Evaluate the intended workflow

This composite story explores a roadmap outcome. Compare it with the implemented product boundary and current release evidence before planning an integration.

What’s your enterprise story?

Tell us what the checklist is costing your team and we will give you a straight answer on fit.