Customer A seeing Customer B's data. That can kill enterprise sales before it becomes public.
WE VALIDATE FLAWS IN LOGIN, BILLING, ACCESS, DATA, AI BEFORE DAMAGE.
Manual pentest for web applications, APIs and Android and iOS apps. A 25-hour Sprint for R$9,500, within 7 business days. We refund 50% if we find no flaw.
100+ real findings
RESPONSIBLE REPORTING, AUTHORIZATION, AND PUBLIC PROOF
Real risks in SaaS with login, billing, data, and AI
One flaw in login, billing, or data is enough to block an enterprise deal.
Paid access released wrong. Billing, authorization, and access need to close together.
Uploads and AI creating hidden cost. Automated tools rarely explain business impact.
What you receive
A report the developer can fix and the decision-maker can read.
Each flaw is explained without jargon: what someone could do, how severe it is on a 0 to 10 score, how to repeat the test and how to fix it. At the end, a letter to show customers and auditors, and we check again what was fixed.
- One-page summary for whoever decides
- Step by step for each flaw, so the developer can repeat it
- Suggested fix, and a second check afterwards
Security test report
Loja Exemplo Ltda
Result
3 flaws found. The most serious let one customer read other customers’ orders. None allows moving money.
Severity of each flaw, from 0 to 10
- 7.1
One customer could open another customer’s order
High · Fixed and checked again
- 6.9
The login screen revealed who has an account
Medium · The client chose to handle it later
- 2.3
The same discount coupon worked twice
Low · Fixed and checked again
How a flaw appears in the report
One customer could open another customer’s order
What could be done: Signed in with an ordinary account and changing a number in the address, any customer could open another’s order: name, address and items bought.
How to fix: The server checks that the order belongs to whoever is signed in before answering. An automated test now tries to open another account’s order on every change.
Instant estimate
See the price and timeline for your case.
A few answers, no sign-up. The package changes as you choose.
Sprint · R$9,500see detailsEstimated quote
Suggested package
Sprint
R$9,500
25 hours of manual testing, delivered within 7 business days. One web application, API or mobile app (Android or iOS) on the flows that matter most: login, permissions, customer data, and payment.
- Why
- One target, few kinds of user and the flows that matter most fit in the 25 hours.
- Timeline
- Runs within 7 business days.
Already included in the price
- Executive and technical reports, with an attestation letter for customers, investors and auditors.
- A second check of your fixes for 90 days, at no cost.
- Up to 3 interest-free installments.
- We refund 50% if the test finds no flaw.
On your side: the signed authorization form and two test accounts.
Answer within 1 business day, with the confidentiality agreement signed the same day. No commitment.
An estimate from your answers. The final price comes in the proposal, after we see the system. RET Tecnologia em Informática Ltda, CNPJ 61.709.429/0001-47 (Brazil).
Security for the people who decide.
When risk touches customers and revenue, the answer is a manual test with proof. The smaller steps help those who are not there yet.
- 01 · SignalPromptbook
First-pass triage to review login, data and billing in AI-built products.
- 02 · ScanAuditMySaaS
In maintenance. Continuous scanning of code, dependencies, infra and web surface.
- 03 · EstimateInstant estimate
Four answers show the package, the price and the timeline for your case.
- 04 · ValidationPentest
Manual test under scope when risk touches revenue and data.
Not time for a pentest yet?
Start by reviewing it yourself, with the Promptbook.
Ready-made prompts for the AI you already use to review login, billing and data in your SaaS. You leave knowing what to fix now and what deserves a manual test.
- Arrives by e-mail after payment
- Offline reader and editable files
- It does not replace a pentest: it shows where to look
FAQ: questions about Promptbook, AuditMySaaS, Risk Review, and manual pentest
No zero-flaw promise. No unauthorized testing.
Question: does the Promptbook replace a manual pentest?
Question: when should I use AuditMySaaS?
Question: how to choose the pentest package?
Question: can the manual pentest be bought directly?
Question: does RET test systems without authorization?
Question: what deliverables come after a review or pentest?
Do data, billing, or B2B customers depend on this?
Direct Contact: Request a security and pentest scope
Directly with the person who defines scope. No commercial layer.
Show where login, billing, or data is exposed. We reply with a next step and clear limits.