Experience

Cloud landing zones, AI governance and pipeline security, delivered in environments where downtime is measured in public consequence: a utility company, a municipal government, a national telecom.

Energy & utilities

AI coding assistants approved, not blocked — across a large engineering estate

Security teams block AI assistants because they touch source code, internal data and developer identity at the same time. Our founder defined the access controls, acceptable-use policy, platform hardening and audit trail that let this utility approve a rollout instead of deferring it — then extended the same governance to agent building and to the models themselves. The secure SDLC work underneath it is what made that defensible.

The secure path became the default one, rather than the reviewed one

AI Security
Coding assistants
Agent governance
Model risk
Secure SDLC
Career engagement

Read the engagement→

A utility companyEnergy & utilities

Public sector

An Azure landing zone with guardrails in place before the first workload arrived

As Ville de Québec moved workloads into Azure, the question was not whether the first environment could be secured but whether the hundredth would be. Our founder designed and implemented a secure landing zone with multi-subscription governance: Azure Policy enforcing regional restrictions, permitted SKUs, NIST SP 800-53 and mandatory tagging; a Hub & Spoke topology with strict network segmentation; RBAC and PIM with Just-In-Time access; secure backup and resilience; and a CAF-based cloud risk register. New subscriptions start compliant instead of being remediated later.

New subscriptions inherit their security controls automatically

Cloud Security
Azure
Landing Zone
Public Sector
Career engagement

Read the engagement→

Clients we have delivered for

Want this applied to your estate?

Tell us what you are working on. We reply within one business day.