Where your software and your data live is your call

If you run a regulated business, or you simply take your customers’ trust seriously, one question tends to come before all the others. Where does the data live, and who controls it.

It is the right question to lead with, and our answer is simple. Where your software and your data run is decided by your data residency, not by our convenience. That might be your cloud, it might be ours, it might be a partner cloud. Whatever the answer, the data and the control stay yours. This post explains what that means in practice and why we built our engagements around it.

Your residency rules come first

Every serious business has constraints on where data is allowed to sit. Sometimes it is the law of a country or a province. Sometimes it is a contract you signed with a large customer. Sometimes it is simply a line you have drawn for yourself about what good stewardship looks like.

Those constraints are the starting point of any build we do, not a box we check at the end. When we map the work at the outset, we map exactly where your data is allowed to live and what rules govern it. The hosting plan is shaped to your residency from the first conversation, so there is no awkward surprise later where the architecture and the rules turn out to disagree.

Where it runs, and who controls it

Once we know your residency, we choose where the system runs to honor it. If your rules say it has to live in an account and a region you own, that is where it goes, and we operate inside it. If it makes more sense to run on our infrastructure or a partner cloud, it still sits in the region your residency requires, under the same rules.

Wherever it runs, one thing does not change. The keys stay where they belong, the data stays auditable, and you can always prove to a regulator exactly where everything sits. We do not quietly route your information through accounts that make us the gatekeeper of your own data. A vendor who holds your data holds leverage over you, and we are careful never to put ourselves in the middle of that.

Best in class partner platforms, and our own infrastructure

We do not build everything from scratch, and we do not believe you should pay us to. We assemble your system from best in class partner platforms, chosen for fit and reliability, and from our own npayload infrastructure where it adds something real.

We are deliberately not naming those partners here, and there is a reason for that. The right set of platforms depends on your residency, your risk profile, and your existing relationships, and it can change. What does not change is the principle. Whatever the building blocks, they are arranged to follow your rules and to keep you in control, never to lock you into ours.

When your software needs to act on its own, we connect it to our own npayload infrastructure. That is what lets it sense what is happening around it, decide, and act, with a hash chained audit trail behind every step. Even autonomy stays inside your boundaries. The system can move on its own and still leave a clear, tamper evident record of what it did and why, in a place you control.

No lock in to us

A studio can capture a client in quiet ways. Build only on infrastructure the client cannot see. Hold the keys. Make the cost of leaving so high that staying is the only option that feels safe. We have watched that pattern, and we refuse to run our business on it.

Our view is simpler. If we have to trap you to keep you, we have not earned the work. So we run your system where your residency requires, we keep the keys where they belong, and we document the architecture clearly enough that another competent team could pick it up. We would rather you stay because we are good at this and because we stand behind what we build.

We run what we build

This is not a hand off. We build your software and we operate it, inside your environment and by your rules. When it is live, we are the ones on the pager. The location is never about our convenience. It is about your residency, and about keeping the people who built the system close to the place it actually runs.

We are a small studio in Montreal, bilingual, and we are early enough that we do not have a row of client logos to point at. So we lead with how we work instead. Letting your data residency decide where the system lives, with no lock in to us, is one of the clearest examples of that. It costs us a little control and gives you a lot, and that trade is the whole point.

If you are wrestling with this, we would love to hear about it.