The constraint
Every new jurisdiction added a fixed infrastructure cost, so compliance coverage and the cloud bill grew together. Leadership had started treating expansion as a cost decision rather than a product one.
What we changed
Filing and calculation had been deployed as one service because they shipped together in 2021. Their load profiles are nothing alike: calculation is bursty and CPU-bound, filing is scheduled and IO-bound. Splitting them let each scale on its own terms.
- Separate compute profiles for burst and scheduled work
- Spot capacity for calculation, reserved for filing
- Per-jurisdiction cost attribution so the next decision has data
Where it landed
Infrastructure spend halved while throughput tripled, and the marginal cost of a new jurisdiction stopped being a blocker.


