Contact Whirly Labs | Code-Led Security Assessments and Penetration Tests

What Happens Next

It helps if your first email says what you are building, what worries you about it, and when you need results. Rough answers are fine, for example:

• We are launching a multi-tenant SaaS platform next quarter, including an AI assistant that can read customer data. Before go-live, we want both a review of the code and dynamic testing of the running platform.
• Our scanners report hundreds of findings that nobody acts on. We want custom static analysis for our code base and frameworks, running in our CI pipeline, and handed over to our team.
• Our product security team is two people short for the next six months. We need experienced analysts who review new features with our developers and work within our processes.
• We are in talks to acquire a software company. As part of our due diligence, we want its software reviewed for security issues, and to know whether it supports what the seller has told us.

1. We reply

   Within one business day, with a few questions about your application and what you want to achieve.

2. We talk

   In a free call with one of our analysts, we go through what the application does, where you see risks, whether we can work with the source code, your timeline, and any compliance requirements.

3. You receive a proposal

   A written proposal sets out the scope, deliverables, timeline, the consultants who will do the work, and the price, in euros, US dollars, or South African rand. The price is fixed for the agreed scope; if the scope changes, we agree on it with you first. Once you accept it, we schedule the kickoff with your developers. How an assessment works.