1. What you are buying
Three plans, described with their current prices on the pricing page. Every plan is paid; nothing that tests your app runs until the purchase is complete.
- Pro covers up to 10 apps for a year: an AI penetration test of a staging app you own when you start, then a retest every month, twelve in the year, with AutoFix and Fix all on the findings, up to 25 fixes a calendar month. It is priced per month and billed yearly in advance, and the term runs for twelve months from the day your payment is confirmed. It renews only when you pay for the next year.
- The one-time engagement covers one app, paid once: an AI penetration test of a staging app you own, a retest to confirm the fixes, and AutoFix, including Fix all, on the findings. It does not renew.
- Enterprise is priced in writing. It can include a fix sprint: a fixed price agreed before it starts, where half begins the work and the other half falls due only on the condition in section 3.
Codebases larger than one repository or spread across several services are quoted after the report and before any money moves.
2. Scope is written down before the work starts
Before a sprint begins we write down which findings are in scope, what "fixed" means for each, and the price. That document governs. Anything discovered later that is not in it is offered as a separate piece of work, never added to the bill.
3. What "green" means, exactly
The balance falls due when your test suite passes three times in a row, each from a clean checkout, in your own pipeline. Not on our machine, not on a screenshot, and not on our word. The second run exists to catch a suite that passes only because of state left behind by the first; the third catches one that passes only in a particular order.
If we do not get you there, you keep every change we delivered and owe nothing beyond the deposit. We do not invoice for the balance and we do not ask you to waive anything in exchange.
Two limits on that promise, so it means something rather than everything:
- It covers the findings named in the scope document. A failure caused by a change you made during the sprint, or by an outage in a service you depend on, is not a failure of the gate.
- It is a payment term, not a warranty of security. No review of any depth can prove the absence of a vulnerability, and we do not claim to.
4. Access, and what we will not do with it
We ask for read-only access to one repository. We do not ask for production credentials and you should not give them to us.
We never execute your code against a live system. The static report never runs it at all. A verification run executes your test suite only inside a disposable container with no access to anything of yours, only after you have asked for it in writing, and only against a repository you named.
You confirm that you are entitled to grant that access: that the code is yours or you are authorised to have it reviewed.
5. Who owns what
Code we write for you during a sprint is yours on payment of the deposit, not on final payment, so a dispute about the balance can never leave you unable to use work you have already paid for.
The report is yours. The detectors, the tooling and the method behind it remain ours. We may describe the class of defect we found in public writing; we will never name you, quote your code or identify you as a customer without your written permission.
6. Payment
Invoices are due on receipt unless the scope document says otherwise. Prices are in US dollars and exclude any tax we are required to add, which will be shown separately. Where a payment provider is used, their processing of your card or bank details is between you and them; we never see or store a card number.
7. Limits of liability
Our total liability for any claim arising out of the work is limited to the fees you actually paid us for the piece of work the claim relates to. We are not liable for lost profit, lost data or business interruption. Nothing here limits liability for fraud, or for anything that cannot lawfully be limited.
8. Ending it
You may stop a sprint at any time. If you stop it before the end, the deposit covers the work done to that point and nothing further falls due. We may stop a sprint if we are asked to do something unsafe, unlawful, or outside what was agreed, and in that case we refund the unused part of the deposit.
9. Changes to these terms
We may change these terms for future work. The version in force for your engagement is the one published on the day your scope document was signed, and we keep the earlier versions so that can be checked.
10. Law and disputes
These terms are governed by the laws of the United Arab Emirates as applied in the Emirate of Dubai, and the courts of Dubai have exclusive jurisdiction. Before either of us files anything, we each agree to put the complaint in writing and give the other fourteen days to answer it.
11. Reaching us
Questions about these terms go to [email protected].