Tenant-resident architecture
OpsWork runs in your Microsoft 365 tenant. SharePoint, Outlook, Teams, Key Vault — all in your perimeter. We never proxy your data through a third party.
Security
OpsWork is designed for a paranoid customer. Every architectural decision favours your perimeter over our convenience. The agents run inside your tenant; we never proxy your data through a third party.
OpsWork runs in your Microsoft 365 tenant. SharePoint, Outlook, Teams, Key Vault — all in your perimeter. We never proxy your data through a third party.
Customer data is only processed by models accessed via your own Azure OpenAI / Foundry deployments. The MCP server refuses requests from any other tenant.
Production processing is pinned to UK South. EU South is the only failover region. No data egress to US or Asia.
Every agent decision logged with sha256-digested arguments. No raw payloads retained. Replayable against test fixtures without retention risk.
No secrets in Function App config, no secrets in environment variables, no secrets in source. Function Apps reach Key Vault via managed identity with 'Key Vault Secrets User' role only.
11-step plan-as-code completes inside 30 days. Erasure certificate issued at the end. Statutory retention (HMRC 6y, professional indemnity 15y, construction records 12y) honoured.
We publish the path, not just the destination. If a control isn't in place yet, it's listed here with the date it will be.
We use only the minimum third parties needed. Each is contracted with a DPA, a UK transfer addendum, and a 30-day breach notification clause.
Webfonts (Manrope, IBM Plex Mono) are self-hosted from this site's own origin — Google Fonts is not a sub-processor.
A current and dated sub-processor list is available on request.
Send us your DDQ / SIG-Lite / your DNO's standard supply-chain questionnaire. We typically return it inside three working days.