Architecture
Why the environment runs in your account and not ours
Hosting your data would be easier for us and worse for you. Here is what changes when the infrastructure sits on your own billing.
The incentive problem
When a vendor bundles infrastructure into a rate, the cost goes opaque and the incentives come apart. Efficiency turns into the vendor’s margin instead of the customer’s saving.
Running in your account at cost removes that. You can see the bill, budget against it, and cap it with your own controls.
What it means for exit
The harder question is what happens if you stop working with us. When the environment is in your account and the infrastructure code is in a repository you can reach, the answer is that you keep it.
There is no repatriation project because nothing was ever held somewhere else.
What it costs us
It is more work. Provisioning into someone else’s cloud organization means enumerating standing access in writing, keeping it reviewable, and building the same foundation identically across customers.
That last constraint turns out to be the valuable one: because the environment is the same everywhere, improvements made on one engagement reach everybody.
Want this against your own numbers?
A scoping call works out which measures are worth baselining and whether your systems can actually be read.
Let’s chat