Code & Architecture Audit
A clear, prioritised read on your code.
A review of your code and infrastructure, with prioritised findings and rough effort for each.
- Typical length1–3 weeks
- How it startsA call to agree what the audit is for
- Who you work withA senior engineer, plus DevOps for infrastructure
- InvestmentQuoted after a short call
Sound familiar?
Problems we fix.
You’ve inherited a codebase
Its authors have moved on, and nobody knows what state it’s in.
A big decision is coming
You’re about to scale, raise or hire, and need to know what the code can take.
Releases keep breaking
Something fails every release and nobody knows where to start.
Deliverables
What’s included.
- Architecture map: services, data stores and third parties
- Code, tests, dependencies and common security weaknesses
- Infrastructure, deploys, backups and cloud costs
- Prioritised findings with rough effort, and a walkthrough call
Timeline
How a Code & Architecture Audit project runs.
- Step 01
Scope call
Agree which decision the audit is for and what’s in scope.
- Step 02
Access
Read-only code, a staging environment and exported logs, no production access.
- Step 03
Review
A fixed number of days reading, running and testing the system.
- Step 04
Report & walkthrough
The written report and a call with your team.
Tools we use
Code & Architecture Audit FAQ
Will you just tell us to rewrite it?
No. We recommend the smallest change that solves each problem, and explain any part we think needs a rewrite.
Is this a penetration test?
No. It covers common security weaknesses, but it isn’t a formal penetration test, a certification or legal due diligence.
Who owns the work?
You do, once the related invoices are paid in full. We keep our pre-existing tools and know-how, and you get a licence to any of it built into your deliverables.
How is it priced?
As a fixed fee for an agreed scope, quoted after a short call. Any scope change, and its effect on cost and timeline, is agreed in writing first. Payment terms are in our Terms of Service.