Code and architecture audit
NDDev audits code and architecture: we check your product’s security, structure, tests, dependencies and infrastructure and hand over a report with findings ranked by risk and a plan of fixes. We check by the same rules we use to build our own projects, and our team has more than 100 of them.
Who it is for
Companies that inherited a product from a previous contractor, are preparing for more load or a major rework, or notice that every change breaks something next to it.
- Security against the OWASP Top 10
- Architecture and module boundaries
- Tests, dependencies and CI/CD
- A report with a plan of fixes
What we check in the code and around it
We start with the whole picture: what parts the product is made of, where the module boundaries run and how data travels from the interface to the database. Then we go down into the code: typing, error handling, duplicated pieces, database queries, caching and test coverage.
- a map of the architecture and dependencies between modules
- code quality: typing, errors, duplication, readability
- security against the OWASP Top 10 and secret storage
- the database: schema, indexes, heavy queries
- tests and their coverage
- build, CI/CD, containers and backups
- a report with findings ranked by risk
- a plan of fixes with effort estimates
We check security against the OWASP Top 10: server-side input validation, parameterised queries, CSP and security headers, secret storage and access rights. Separately we look at build and deployment: image versions, how containers run, backups, and whether a new team could deploy the product from its documentation.
Every finding gets a risk level, an explanation and a recommendation. We report critical findings at once, ahead of the final report.
How the audit runs
We need read access to the repository and, where possible, to the server.
Goals
We find out why you need the audit: growing load, a change of contractor, preparation for a major rework.
Architecture review
We study the structure, documentation and infrastructure and draw a map of modules and data.
Code review
We check the code, security, database and tests and run the project from its own documentation.
Report and discussion
We hand over the report with findings and a plan of fixes and go through it with your team on a call.
Questions about a code audit
Which languages and stacks do you audit?
The ones we write ourselves: TypeScript and JavaScript with React and Next.js, Python with FastAPI, Go, Flutter, C++ and Rust, and PostgreSQL and Redis databases. If your stack is outside this list, we will say so on the first call.
What do we get at the end?
A report: an architecture map, a list of findings with risk levels and explanations, and a plan of fixes with effort estimates. You can give the fixes to us, to your own team or to another contractor.
How much does an audit cost?
The price block gives the lower bound. The figure grows with the size of the codebase and the number of services, and when the infrastructure is in scope. We give the exact scope and timeline after a first look at the repository.
Do we have to pause development during the audit?
Your team keeps working as usual. We review a fixed version of the code and check our findings against the latest changes before the report.
Will you fix what you find?
Yes, if you want us to. After the audit we propose the scope of fixes with a price, and it works well in stages, starting with the critical findings.
How do you handle our code?
We take read-only access and work in your repository. After the audit you revoke the access, and we fix the confidentiality terms in the contract.
from ₽84,000
- Free warranty
- 12 days
Prices are starting prices for information only and are not a public offer. The final price is fixed in the specification.
Software consulting
Related
Tell us what worries you about your product
Describe the product, the stack and the reason for the audit. We will name the scope of the review and the price.
We reply within 24 hours