Four things. We write your login, we design what it runs on, we handle the encryption and the keys, or we read what you already have and tell you where it leaks.
Login looks like a solved problem until the constraints show up. We design the protocol for your case rather than bending a library around it, including our own challenge handshake where a normal bearer token would not survive the threat model.
The boxes and pipes underneath the app. The goal is boring: when one thing gets popped, the attacker should find a locked door behind it instead of your database. Runs on your cloud account or your own hardware, written down as code rather than as a wiki page someone forgot to update.
Encrypting data is the easy half. The hard half is where the key lives, who can reach it, and what happens the day someone has to rotate it. We write the scheme for your constraints, in our own library when the available ones get in the way, and we build it so that losing us does not mean losing access.
The cheapest thing we sell, and usually where we start. We read the code and the config the way somebody attacking it would, then tell you what actually needs fixing this week and what you can live with for now.
A focused review starts at 890 EUR, a login build at 2,400 EUR, encryption work at 1,500 EUR. The full list, including retainers and day rates, is on the pricing page.
Including the part most quotes leave out: what we are not doing.
Signed before anyone gives us a password. Our access is scoped, and it dies with the project.
Pull requests your team reviews, and rejects when we get it wrong.
Whoever writes your code also answers your mail. Nobody is forwarding it.