Architecture review
Service boundaries, data model, coupling and failure modes, assessed against where the business is going rather than against a textbook.
Technical Consulting
Software Architecture and Technical Consulting
Sometimes you do not need a team — you need an honest answer. Whether the platform will hold at ten times the load, whether the codebase you are about to acquire is worth what you are paying, whether the rewrite your team is proposing is necessary. We review, we measure, and we write it down in language a board can read.
What's included
Code and delivery review
Code quality, test coverage, branching and release process, and the practical reasons your team's delivery has slowed down.
Infrastructure and security review
Cloud configuration, access control, secrets, backups and restore testing, dependency and vulnerability posture.
Performance audit
Profiling the paths that are actually slow — queries, N+1s, cold starts, cache misses, front-end Core Web Vitals — with measured before-and-after.
Scalability and migration planning
Capacity modelling, cost projection, and a sequenced migration plan with the risky steps isolated and reversible.
How we work
- 01
Framing
We agree the decision the review has to inform. A review without a decision behind it produces a document nobody acts on.
- 02
Access and discovery
Read access to the repository and infrastructure, plus interviews with the people who run it day to day.
- 03
Assessment
Static review, profiling and load measurement, with findings ranked by risk and by cost to fix.
- 04
Report
A written report: what is fine, what is a real risk, what it would take to address, and what we would do first.
- 05
Walkthrough
A session with your team and, where useful, a separate one for non-technical stakeholders.
- 06
Optional execution
If you want us to implement the recommendations, we can — but the review stands on its own and is priced separately.
Technology we use for this
- PostgreSQL
- AWS
- Docker
- Kubernetes
- GitHub Actions
Frequently asked questions
- How long does a review take?
- Typically one to three weeks depending on the size of the codebase and how much of it is in scope. Focused audits — a single performance problem, one security question — can be shorter.
- Will you recommend a rewrite?
- Rarely. Most systems that feel unsalvageable have three or four specific problems that can be addressed incrementally, and a rewrite is usually the most expensive way to fix them. When a rewrite genuinely is the right call, we will show the reasoning.
- Do you do technical due diligence for acquisitions?
- Yes — code, architecture, infrastructure, security posture, team dependency and technical debt, reported in terms an investment decision can use.
- Do we have to hire you to implement the findings?
- No. The report is yours and is written so your own team or another vendor can act on it.
- Can you work with our in-house team?
- Yes. The most useful reviews are done alongside the team that built the system, not over their heads.
Book a technical review
Tell us the decision you are trying to make and what you are worried about. We will propose a review scope and what it will answer.
Start the conversation