Every question, answered in writing.
What buyers, security teams and legal ask before they commit: how continuous works, what it costs, what we touch, and where data lives.
How it works
What is continuous autonomous pentesting?
Agents pentest your web app and API on their own: a lead plans and stays off the target, engineers take one slice and come back with a working exploit, and testing only touches hosts you authorized in writing. Starter is one full pentest a month; on Growth and above, a pentest follows each release you approve.
See the product →How is this different from a scanner?
A scanner lists what might be there; you verify every flag yourself. We prove what an attacker can actually do on the live system: PoC, severity, retest after you fix. Scanners still have a job. On Growth and above, a pentest follows each release you approve.
Start my free check →How is this different from a bug bounty?
Fixed scope, fixed price, report on a timeline. A bounty has no coverage guarantee and no cadence. You need a dated report for SOC 2 and customer questionnaires; that is what a Rheono pentest produces.
Sample report →Does it plug into CI/CD?
Yes. On Growth and above, your pipeline can start a pentest after a release you approved. Light monitoring keeps running between releases. The portal shows each surface's status and findings.
See pricing →How fast do I see findings?
The free check is read-only and takes about 20 minutes; the written report arrives within one business day. On a paid plan, the first pentest typically lands within the first cycle after authorization is signed and the plan is live. Exact timing depends on surface size.
Start my free check →What happens if you find a critical?
We pause the affected path. You hear about it immediately, and at the latest within 24 hours of verification, on the agreed channel. Nothing destructive runs without written sign-off.
Sample report →Pricing
What does it cost?
Published flat tiers: Starter €99/month (one full pentest a month), Growth €499/month (continuous on one app), Pro €999/month, Business €2,499/month. Annual prices are on the pricing page and cost less than twelve monthly payments. No per-scan fees. On Growth and above, more pentests do not raise the bill.
See pricing →Will my auditor accept the report?
Your auditor decides. You get a signed report with scope, method and CVSS-scored findings, each with a working proof of concept. cSquare GRC, our GRC partner, maps it to your controls. Neither of us certifies you. If a contract requires a BSI- or CREST-accredited tester, tell us at scoping.
Pentest to audit →What is included?
Onboarding and scoping in the portal, validated findings with PoC, retests on the plan surface, and a downloadable report. Retests of fixed findings are not an add-on meter.
Trust →Can I cancel or change plan?
Monthly plans renew until you cancel in the billing portal. Upgrade or switch interval there as well. Annual is billed up front for the year.
Account billing →What moves the price?
Surface count and cadence. Starter is one full pentest per billing period on one app; Growth and above are continuous, and your CI can start a pentest after a release. Before the first pentest you verify domain ownership (DNS TXT on `_rheono` or a well-known file) and sign the written authorisation. Bigger estates move to Pro or Business. Beyond that, or for a protocol or desktop client, a scoped engagement adds fixed-price modules to a plan, in writing.
See pricing →Scope & safety
What surfaces do you cover?
External web apps and APIs you authorize in writing, and nothing else. Internal networks, mobile binaries and social engineering are out of scope for the pentest sold here. The engine itself already carries MCP servers, mobile and AI-agent testing; each is being opened up as a sold surface in turn.
Pentest page →Is the free check safe?
Read-only: at most ~300 page requests at ~1/sec from one US IP. No logins, no exploit payloads, no port scanning. Permanent opt-out is one word. The full method is on the How we check page.
How we check →Can you also look at our source code?
Yes as a flat add-on, in writing. With repo access the agent reads each release diff for data-flow and auth issues; findings include file:line plus a working PoC.
Contact →Who signs the report?
Rheono signs every report: Advanced electronic signature (eIDAS, PAdES-B-T) + RFC 3161 timestamp, with NIS2 / ISO 27001-ready evidence mapping and CVSS. Samir Abis is the person named in your contract and accountable for it. It is not an audit opinion: only your auditor signs the SOC 2 report or the ISO 27001 certificate.
Trust →Data & trust
Where does our data live?
Reports and evidence are stored in the EU (Google Cloud, Belgium). Testing and analysis run from US servers (Google Cloud, Iowa). Sub-processors: Google Cloud, Neon (database), Resend (email), Stripe (payments), and PostHog Cloud EU (Frankfurt) for site analytics, only after your consent. Encrypted in transit and at rest, least-privilege access, append-only logging.
Privacy →How does GDPR work here?
You are the controller, we are the processor, under a DPA (Art. 28 GDPR). A data-protection incident is reported to you within 24 hours.
DPA (Art. 28) →What happens to the findings and the report?
The report is signed with an advanced electronic signature (eIDAS, PAdES-B-T) plus an RFC 3161 timestamp, and kept for 10 years. It is yours.
Sample report →Who is accountable if something goes wrong?
Insurance: €50M per claim, without deductible (AGB §14). Before anything runs, your written authorization with rules of engagement is in force for 90 days.
Trust →Something not answered here?
Ask it directly; a named person answers, in writing, the same day.