Shibase
A freelance marketplace in the Netherlands asked whether its backend, database, infrastructure and mobile app were ready to launch. Not yet: here's what was found and fixed.
Find what breaks before customers do.
Shibase was close to launch: a Go backend, a database, cloud infrastructure and a mobile app. Before opening it to real users, they wanted an outside engineer to go through all of it and say plainly what would fail first.
I reviewed the code, the data, the configuration and how it was deployed, wrote down every finding with what to do about it, and checked the fixes before signing it off.
What the audit found.
Security vulnerabilities
Weaknesses that are invisible in a demo become the first thing an attacker finds after launch.
Each one was written up with how to fix it, fixed, and checked again before sign-off.
Database access
Who and what can reach the database, and with which rights, decides how bad any other mistake can get.
The access problems were written up, put right and checked before launch.
Deployment
A launch is only as safe as the way new versions reach the servers and how quickly a bad one can be undone.
The deployment gaps were closed, and the platform was signed off for production.