Risk audit, before anything breaks.
We look at your system's code, security and infrastructure, and tell you in writing where the biggest risk is and what to do first. The fee is deducted from a follow-up project.
Ask for a risk audit
When it makes sense
- You inherited a system and don't know what's inside.
- The previous developer left, and the documentation is thin.
- Nothing has been updated for a while, and you don't know how bad it is.
- You are about to invest in development and want to know what you are building on.
An audit tells you where you stand before you spend money.
What we look at
Code
Quality, structure, outdated parts, hidden bugs.
Security
Known vulnerabilities, permissions, how passwords and keys are handled.
Infrastructure
Servers, updates, resources, availability.
Backups
Whether they exist, whether they work, and whether you can restore from them.
Dependencies
Outdated packages and plugins, licences.
Logs
What the logs show: errors, slowdowns, suspicious events.
What we find in the logs is money
While taking over a webshop, we spotted in the logs that a hidden payment bug had been costing it customers for four years. The damage was nearly half a billion forints. The fix took a few hours.
Read the caseHow it goes
- 1
Access
We ask for access to the code, the server and the logs.
- 2
Audit
We go through the code, the server, the backups and the logs.
- 3
Written report
Starting with the biggest risk, with a suggested order.
Do you know what's in your system?
How can we help? We reply within one business day.