The homepage sells the outcome. This page is for the person who wants to know what actually runs underneath it — nine layers, each documented, monitored and owned by you.
Identity
Microsoft Entra ID · Google Workspace identity
Every user, device and application authenticates through one identity provider, with MFA and Conditional Access enforced, privileged access controlled and sign-ins monitored. Identity is where most breaches start, so it's where the baseline starts.
Email, files, chat and collaboration in your own tenant, configured to a documented baseline: sharing defaults, external access, retention, legacy protocols off. Backed up separately, because the platform doesn't do that for you.
Remote monitoring and management · Managed endpoint detection and response
Every laptop and desktop enrolled in device management, encrypted, patched on a schedule, protected by managed EDR, and monitored for health and security around the clock.
Web application firewall · DNS filtering · Email security · Vulnerability scanning · Password vault
Layered controls across identity, endpoint, email, DNS and web, run as a Prevent → Detect → Respond → Recover loop. Logged centrally so we can answer 'what happened?' with evidence.
Enterprise cloud where the workload needs it; cost-effective UK and European infrastructure for everything else. Least-privilege access, private networking, infrastructure defined in code where it earns its keep.
Immutable backup platform · Microsoft 365 / Google Workspace backup
3-2-1 architecture with immutable, isolated copies. Every protected system has defined recovery targets, a scheduled test restore, and a record of the result — Foundry Recovery Assurance.
Business numbers in the cloud, ported and registered to you, with routing, queues, recording and mobile failover. Teams-native calling where the team already lives in Teams.
Infrastructure, endpoint, backup, certificate and uptime monitoring
One place where everything we run reports in. Alerts become tickets automatically, and the monthly report you receive is generated from the same data we use to run your environment.
We name the platforms you’d own an account with — Microsoft, Google, the cloud providers — because those are yours. We describe the operational tooling we use to run environments by category rather than brand, partly because we choose tools on merit and replace them when something better exists, and partly because publishing a full stack diagram of every customer’s security tooling is not a favour to anyone. Ask on the call and we’ll tell you.
Find out what your technology is actually costing you.
Thirty minutes with an engineer about your current environment: the biggest risks, the inefficiencies, and what you’re paying for that you don’t use. No obligation, no sales script. See what the first call covers.