04 What you own
Cancel us on a Friday. Monday still works.
The walk-away test: if we disappeared tomorrow, would your data platform keep running? It should, and here is what that means in practice.
What is yours
The repository
Every line of pipeline, model, report and infrastructure code lives in a repo you own, from the first commit.
The infrastructure
It runs in your cloud accounts, under your credentials. There is no dyad data runtime in the middle.
The documentation
Decision records, runbooks and a data dictionary ship with the code, so the why survives the handover.
The credentials
Secrets stay in your secret store. Code holds references, never values, and rotation is yours.
The handover
It is not an event at the end; it is built up as we go.
Documentation pack
Architecture overview, decision records, runbooks for the things that break, and a generated data dictionary.
A recorded walkthrough
Your team can watch it again when someone new joins.
Access clean-up
A checklist of every credential and permission we used, removed or rotated by your team.
Optional support
Available if you want it. The platform never depends on it.
The four tests
It runs in your accounts
Your cloud, your warehouse, your credentials.
Any real engineer can maintain it
Open tools, readable source, standard conventions. Ours, your in-house team, or the next person you hire can pick it up and carry on.
It explains itself
Decisions and runbooks travel with the code.
Nothing to unplug
No proprietary platform to leave. Staying is a choice, not a dependency.
If you stop
Your team carries on with what it has. If you want help later, we pick up from the same repo and the same documentation as anyone else would. We do not hold anything that makes that harder.