TL;DR. Hands-on DevOps for Toronto and Waterloo teams. I deliver it remotely from Ottawa, inside their tools and cloud account. The worked example is platform rails around inference.
The account already picked the architecture
Nobody hands you a blank cloud account and a Toronto office. They hand you the account that already has a billing owner, an identity provider, a VPC, and a product repo. That constraint picks the architecture. The city does not.
I work inside the Toronto or Waterloo team’s account from Ottawa. The identity provider, the repo, and the bill stay theirs.
Remote across Canada is the same engagement. On site stays selected, for the jobs where being in the room is the work.
Remote does not change the rails. It changes the test for the gates.
What remote changes
If a gate only holds while I am on a call, it was a suggestion. A teammate in Toronto or Waterloo has to run the next batch without asking. Distance makes a fake gate obvious sooner.
The pattern is written up in Platform rails around inference: constraint first, gates so AI can draft while humans still ship. Same test as the Holtwick loop: the gate is what you actually shipped.
Handover
The engagement is done when a teammate can drive the rails and the gates fail closed.
I take selected, forward-deployed platform work of this shape. Available Q4 2026. Remote from Ottawa. Hire a DevOps contractor and propose a time.