Services

Our services

Our work is organised into three practices. Every service has a defined scope and clear deliverables, and every engagement is led by a 9fold principal architect, with specialist engineers added where the work needs them.

Architecture

Architecture and assurance

Senior technical leadership for programmes, and an independent view on the work of others.

Architecture leadership

A 9fold principal joins your programme as lead or principal architect. They own the current, transition and target-state architecture, chair design authority, hold suppliers to account and give your senior leaders a clear technical view.

Typical length
6 to 12 months, often extended
Team
Principal architect, with specialists as needed
You get
High- and low-level designs, a running design authority, architecture standards and a decision log

Independent assurance

When a supplier is designing or migrating something for you, we act as your independent technical authority. We review designs for security, resilience, operability and cost before they’re approved, and raise delivery risk early and in writing.

Typical length
A one-off review, or ongoing through delivery
Team
Principal architect
You get
Written assurance findings for your governance boards and a technical voice on your side of the table

Discovery and Alpha

Technical leadership for new services working through the GDS Service Standard. We frame the options, test the riskiest assumptions with working prototypes and prepare the architecture evidence for assessment.

Typical length
8 to 12 weeks per phase
Team
Principal architect, alongside your multidisciplinary team
You get
Options analysis, prototypes, a target architecture and assessment-ready evidence

Bid and solution design support

For delivery partners bidding for public sector work. We write and review the technical solution, produce the architecture diagrams and check your response against what the buyer has asked for.

Typical length
Per bid, usually 1 to 3 weeks
Team
Principal architect
You get
A technical solution narrative, architecture diagrams and a review against the evaluation criteria
Platforms

Platforms and security

Secure cloud platforms that delivery teams can build on quickly, and security teams can evidence.

Organisation and guardrailsAccount structure, service control policies, single sign-on
SecurityLog archive, audit, threat detection
NetworkTransit Gateway, central ingress, WAF
Shared servicesPipelines, hardened images, secrets
DevelopmentWorkload accounts
TestWorkload accounts
ProductionWorkload accounts
Illustrative. A typical multi-account landing zone: guardrails set once at the top, shared security and networking in the middle and workload accounts that delivery teams own.

Cloud foundations

We design and build secure, multi-account AWS and Azure environments: account structure, guardrails, networking, identity, ingress and logging, aligned to Secure by Design and NCSC cloud security principles.

Typical length
6 to 12 weeks
Team
Principal architect and 1 to 2 platform engineers
You get
A working landing zone, written as Terraform, with guardrails, ingress patterns, logging, runbooks and decision records

Platform engineering

Internal platforms that make the secure way the easy way for your developers: Kubernetes on EKS and AKS, Terraform modules, CI/CD pipelines and self-service tooling such as hardened image vending.

Typical length
8 to 16 weeks
Team
Principal architect and 2 to 3 platform engineers
You get
A working platform, reusable modules and pipelines and documentation your own teams can own

Security architecture

Security designed in from the start: Secure by Design patterns, preventive and detective controls, centralised ingress protection, identity and log ingestion into Microsoft Sentinel, with designs that stand up to your security assurance process.

Typical length
4 to 12 weeks, or ongoing
Team
Principal architect
You get
A security architecture, control mappings and the design evidence your assurance process needs

Migration and modernisation

We plan and lead moves between on-premises, private and public cloud, from SAP, banking and global multi-region applications to high-performance computing and large datasets, keeping security, governance and recovery objectives intact throughout.

Typical length
Planned in phases, from 3 months
Team
Principal architect and migration engineers
You get
A migration architecture, a phased plan with dependencies and risks and hands-on delivery
Optimisation

Optimisation and capability

Getting more from what you already run, and building the team to run it yourselves.

Well-Architected and cost reviews

Fixed-scope reviews of an AWS or Azure estate or workload, at a price agreed up front. Our founder has led these reviews for retailers and public bodies, on both AWS and Azure.

Typical length
2 to 3 weeks
Team
Principal architect
You get
Findings ranked by impact and effort, with a remediation plan your teams can carry out

Data platforms

Analytics and data platforms on AWS using Glue, Redshift, Aurora and OpenSearch, and the safe migration of large or critical datasets.

Typical length
6 to 12 weeks per phase
Team
Principal architect and a data engineer
You get
A target data architecture, working pipelines and a migration plan

Building cloud teams

Help to build your own cloud capability so you rely less on suppliers: role design, hiring support, learning pathways, mentoring and setting up design authority. Our founder helped grow a cloud consultancy from four people to more than 50 and started an academy for people new to tech.

Typical length
3 to 6 months, often alongside other work
Team
Principal architect
You get
A skills framework, learning pathways, mentoring for your architects and engineers and a plan to hand over
Working with us

What an engagement looks like

  1. Before we start

    A written scope, the price or day rate and the names of the people you'll get. Nothing begins on a handshake.

  2. Week one

    We meet the people involved and read what already exists. By the end of the week you have a short written plan and our first list of risks.

  3. Every week

    A one-page update: decisions made, risks and what happens next. Anything serious reaches you the day we find it.

  4. At the end

    A handover pack of designs, runbooks and decision records, and a session to walk your team through it.

Technical depth

What we work with

Foundations
AWS Organizations, Control Tower, service control policies, Transit Gateway, Direct Connect, ExpressRoute, multi-account landing zones
Security
AWS WAF, Firewall Manager, IAM, Microsoft Entra ID, Microsoft Sentinel, HashiCorp Vault, CloudTrail, CIS-hardened images
Data and integration
API Gateway, Lambda, RDS, Aurora, Glue, Redshift, Database Migration Service, DataSync, FSx, OpenSearch
Platforms and delivery
Kubernetes on EKS and AKS, Helm, Terraform, GitLab, Jenkins, Ansible, Grafana, high-performance computing
Beyond public cloud
On-premises estates, private cloud on Nutanix, VMware, hybrid connectivity, Amazon WorkSpaces and Connect
Standards
GDS Service Standard, Technology Code of Practice, Secure by Design, NCSC cloud security principles, AWS and Azure Well-Architected
Commercials

Ways to buy

Fixed scope

A defined outcome at a price agreed up front. Suits reviews, foundations and Alphas.

Capacity

Named 9fold people on a day rate, under a statement of work. Suits architecture leadership and migration.

Through a partner

We subcontract to the consultancy or integrator already delivering your programme. How this works

Not sure which service fits?

Describe the problem and we'll suggest the smallest engagement that would solve it.