Approval gates
Nothing reaches production until a named person approves it.
Forge
Forge is the system behind all our work. AI agents handle analysis, building and testing, each task goes to the model best suited to it, and a senior person approves every stage.
How it works
Analyst agents + senior lead
Agents read your policies, specifications and existing systems, then draft user needs and requirements in hours. Our lead checks every one.
Requirements · Risks · Assumptions
Architect agents + senior lead
Agents propose designs that follow the Technology Code of Practice. A senior architect chooses one, adapts it and signs it off.
Design decisions · Threat model
Builder agents + senior lead
Agents write code and content in small changes. A senior reviewer approves each change before it ships.
Code changes · Infrastructure as code
Tester agents + senior lead
Agents test for bugs, accessibility problems and security gaps, and check AI features for accuracy and bias.
Test results · Accessibility report · AI evaluation
Release agents + senior lead
A person approves each release to your cloud, and any release can be rolled back. Documentation is written as we go.
Release notes · Runbooks · Transparency record
Safeguards
We built Forge for organisations that answer to auditors, regulators and boards.
Nothing reaches production until a named person approves it.
We record which model produced each piece of work and who reviewed it.
Each requirement links to the code that meets it and the tests that check it.
Automated WCAG 2.2 checks run with every set of tests. A failure stops the release.
We scan dependencies, secrets and code, and test AI features for prompt injection and data leaks.
Client data stays in the regions and cloud accounts we agree with you.
Forge Guard
We are packaging these safeguards as Forge Guard, so security teams can assess and control agents built by anyone.
Choosing models
We test models on each type of task and use the one that does it best: the most capable models for design and complex code, faster ones for tests and documents, and open models on your own infrastructure when data must stay there.
What you receive