Services
Choose a review, an implementation or ongoing support.
Before work starts, we agree the scope, deliverables, schedule and price in writing.
Security and architecture review
For a company that runs on cloud accounts, hosted applications and a few third-party services and wants to know where it actually stands.
| Scope | Cloud accounts and billing, identities and access, networks and exposure, data stores and backups, deployment pipelines, secrets handling, monitoring and alerting, the vendors you depend on. |
|---|---|
| How | Read-only access only. We inventory what exists, test what we can without changing anything, and interview the people who operate it. |
| You receive | A findings report with evidence for every item, ranked by likely impact and urgency; a remediation plan with effort and order; a one-page summary for owners; a working session to walk through both. |
| Schedule | The schedule is agreed after the initial scope and access requirements are confirmed. |
Implementation
For the agreed changes from a review, or for a well-defined build: a new environment, a migration, a pipeline, a recovery setup.
| Scope | Identity and access design, backups and tested recovery, deployment pipelines, monitoring, secrets handling, network boundaries, cost controls, documentation. |
|---|---|
| How | Every change goes through version control and review before it touches production, with a documented recovery step that is tested where feasible. Access is granted per task and returned after it. |
| You receive | Working systems, their documentation, the record of every change, and a handover session for whoever operates them next. |
| Schedule | The schedule is agreed after the initial scope and access requirements are confirmed. |
Retainer
For keeping what was built in good order without hiring for it.
| Scope | Patching and upgrades, monitoring and alert response, access reviews, backup verification, vendor and cost checks, small changes within the month's allowance. |
|---|---|
| How | Agreed response hours, a shared log of everything done, and the periodic written reviews of risks, costs and what to change next that the agreement sets out. |
| You receive | An agreed monthly price, a named contact, and a running record you can hand to an auditor, an insurer or a buyer. |
| Schedule | The agreement sets the monthly scope, response hours and notice period. |
Secure access for AI assistants
Coding and operations assistants can now open pull requests, run deployments and answer support questions. The question is how they get access without anyone handing over passwords or tokens, and how you see what they did.
| Scope | A credential boundary between the assistant and your providers: typed, allow-listed actions; secrets held outside the assistant's reach; a record of the actions taken; revocation in one place. |
|---|---|
| How | We design the boundary around the tools you already use, build it from reviewed components, and prove it with negative tests: what the assistant cannot do matters as much as what it can. |
| You receive | A working boundary, its policy in version control, the action record, and a short guide for the people who approve what the assistant may touch. |
| Schedule | The schedule is agreed after the initial scope and access requirements are confirmed. |
This is how we run our own operations, and the pattern we built first for ourselves.
Not sure which one?
Start with a conversation. If a review is the right first step we will say so; if a single afternoon of implementation solves your problem, we will say that instead.