An intro call
We work out together what is most at risk, what to test first, how deep, with what code access and when. Then we quote for exactly that.
Services
There are no packages, and you don’t need to know what to ask for. We talk through what you’ve built and what worries you, and we judge where an attacker would get the most out of it. The test is built around that. The price is agreed before testing starts and does not change.
Not sure what you need? Most teams aren't. These are the situations we hear most often, and where we would usually begin.
We start with your highest-risk surface: usually where people sign in, where money or personal data moves, and whatever is open to the internet. You come away knowing where you stand and what to fix first.
We test what's going live, the web app and the APIs behind it, and give you a report you can share with the customer who asked.
We test the feature and everything it can reach: what it can be talked into, which tools and data it can touch, and what it could leak.
DORA, NIS2, ISO 27001, SOC 2. We scope the test to what the requirement asks for, and write the report for the auditor as well as your engineers.
Most apps touch more than one. How much of each, how deep, and whether it is one test or a recurring one is what the first call is for.
Your web app and the APIs behind it, tested as each of your user roles: authentication, authorization, business logic, data exposure and tenant isolation.
Chatbots, copilots and agents that call tools: prompt injection, data leaking through the model, tool abuse and excessive agency.
How your app reaches its cloud: roles, keys, service accounts and the paths between them, on AWS, Azure or Google Cloud.
Whitebox testing requires read access to your source code. We settle which one fits on the first call.
We read how your code handles data and permissions, then prove what we find against the running app. It goes deeper in the same time, down to flaws a blackbox test cannot reach. This is what we recommend.
We test the running app from the outside, the way an attacker would. Useful when code cannot be shared, but it sees less in the same time.
However we scope it, it runs the same way and ends with the same deliverables.
An intro call
We work out together what is most at risk, what to test first, how deep, with what code access and when. Then we quote for exactly that.
Written authorization
Signed before any testing, naming targets, dates and contacts.
One lead, start to finish
The same researcher scopes, leads, reports and debriefs. Agents work where we send them, and nothing they turn up reaches your report until a researcher has checked it.
Same-day critical findings
Anything critical reaches you the day we find it.
Report with proof and fixes
Ranked findings, steps to reproduce and a fix for each.
Debrief and retest
A call with your engineers, then a retest once the fixes are in.
Keep running it: it catches problems early. It reads your code and suggests what might be wrong. We test your app as it actually runs, including the frameworks and libraries underneath it, and a researcher verifies every finding before it reaches your report, with its impact and a fix.
Yes. Most teams we talk to don’t. The intro call is free and takes thirty minutes: tell us what you’ve built, and we work out where an attacker would get the most out of it and what to test first.
We recommend it. With read access to your code we go deeper in the same time. If it can’t be shared, we test the running app from the outside.
Yes, to open-source models served by EU providers in EU datacenters. Never to a closed model behind an AI vendor’s API, and your code and data are never used to train a model.
No. Nothing is tested until you sign a written authorization that names the targets, the dates and who to call.
Quote
The call and the quote are free and do not commit you to anything.
Book a call with us