One purpose-built platform for reporting, client delivery and QA, end-to-end encrypted on your own database, domain and mail server. Less admin, more time testing, and a client experience that matches the quality of the work.
Keep the report template you use today. Leave behind messy Word documents, white-label fees, home-built platforms and third parties holding client data.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reports? Get our free, open-source reporting tool
Demonstration portals. The four firms are invented; every screen is the real software.
Hours spent formatting reports, a separate process for every stage, a review that depends on who is free, and a client who only ever sees a PDF. Here is what each of those becomes once the engagement runs through one system.
This is the software running at four firms that set it up differently. Their domain, their logo, their colours, their severity scale, their typeface. Follow one engagement through: the page a client signs in to, the desk your testers work at, and what that client reads when you release it.
Demonstration portals. The four firms are invented. Every screen is the real software.
On your domain, with your logo, your colours and your wording. There is no Pental branding on the page they sign in to, and none on any page behind it.
Calderwood SecurityWhat their client signs in to

Every engagement in flight, who leads it, what is waiting on QA and what is ready to go out. The number your team argues about is on the screen rather than in somebody’s head.
Calderwood SecurityTheir team

Severity, CVSS, category and status on one row. Two switches decide the rest: whether a finding is still a draft, and whether the client can see it yet.
Calderwood SecurityTheir team

Standing access rather than a PDF in an email. They see their own assessments, their open findings and what they have already fixed, and they can come back next quarter.
Calderwood SecurityTheir client, signed in

What was found, what it means, the evidence behind it and what to change. The same record your report renders from, so the two cannot disagree.
Calderwood SecurityTheir client, reading a finding

Nothing above is a theme we chose for them. This firm changed the accent, both theme colours, the whole severity scale and the typeface, from the same settings screen.
VantrellTheir team

A light theme, a teal accent and a severity scale repainted for a firm whose clients are utilities and insurers. Same table, same code, same release two minutes ago.
Thornbury CyberTheir team

Screenshots, code snippets, requests from Burp and tables, pasted as rough as they were captured. One button explains each piece and captions every screenshot, brings in your library's own wording where you have written the weakness up before, and writes the rest: title, description, remediation, score, classification, affected assets, your own fields and the references.
Hosts, ports and payloads come straight from the evidence, so nobody retypes them.
01 of 05
Paste Your Rough Notes
Notes, tool output, tables and screenshots go into the evidence as rough as they were taken mid-test. Nothing else on the finding is written yet.
Calderwood SecurityTheir team, writing a findingEvery prompt is yours to edit, and it runs on your own key or a local model.Demonstration portals. The four firms are invented; every screen is the real software.
A delivery platform holds the most sensitive thing a firm has: its clients' vulnerabilities. So Pental holds only what it takes to run your account. You own your data: everything your clients trust you with lives in your own database, in your own cloud, on a server of yours or on Supabase Cloud, in a region you pick, and Pental has no access to it. The testing work in it is also end-to-end encrypted: read straight from the database, it is unreadable.
If Pental were breached, your clients' data would not be in it.
See exactly what an attacker would getIf your own database were breached, the testing work in it would be unreadable.
Read the full architectureTen areas, each answering one question properly instead of all of them briefly. Start with the platform, or with the question your firm asks first.
Report is Pental's reporting on its own, free and open source on your own server. The Portal is all of Pental.
curl -fsSL https://pental.io/ report/ install.sh | shPentest management and the testing calendar, AI that drafts from your evidence on your own key, the PDF or your own Word template, and retests.
Get ReportAdd or remove testers whenever your team changes, pro-rated, from your dashboard. The rate falls with every tester you add. Prices include VAT, billed monthly, and you can cancel any time.
Your database is yours with either, and everything in Report moves to the Portal with you when you want the rest.
Most of them start with where the data goes, so the answers do too.
A delivery platform for penetration testing firms: one purpose-built system for reporting, QA, client delivery and retesting, with phased engagements, a findings library and a client portal around it.
It runs end-to-end encrypted on a database you own, the AI runs on your key or entirely locally, and everything your clients see is your brand. Every feature is included, priced per tester, and the rate falls as your team grows. The reporting on its own is free: our open-source reporting tool runs on your own server.
Walk through the platformYes. Scanner output comes in as findings in sixteen formats, Nessus, Burp Suite, OpenVAS, Qualys, Nmap and OWASP ZAP among them: one finding per issue with every affected host listed, in your library's wording where it has the issue, and nothing written until you have seen what the file holds.
Findings go to your clients' own Jira, ServiceNow, Azure DevOps, GitHub, GitLab or Linear in one click, or automatically once the report is delivered, the ticket's state is read back every hour, and a closed ticket asks your team for a retest rather than closing the finding. Notifications go by email, with a switch for each event.
Every integrationOn your first engagement. Setting up your portal is a stepped wizard in your Pental account, and the generated PDF is there from the start if you want an engagement running before anything else is in place.
Your own Word report becomes the template: set the variables on it yourself, or let the Document Builder place them for you. Cover page, styles, headers and appendices stay as you built them, and rendering is deterministic, so the same engagement produces the same document every time. That matters when a client puts this quarter's report next to last quarter's.
Watch the setup guideYour data lives in a database you own, in one of three places: PostgreSQL in your own cloud (Azure, AWS, Google Cloud or a server of yours), a self-hosted Supabase stack on a server you run, or a Supabase project in your own account, the quickest way to try it. You own your data, and Pental has no access to your database: it holds only what runs your account, and none of your clients' work. The testing work is also end-to-end encrypted in your team’s browsers before it is saved, so read straight from the database, it is unreadable.
You do not need to know Postgres to run it. Setup is a guided step that checks each stage from your browser as you go, each of the three has a full written guide with its pros and cons, and if you change your mind later, your dashboard moves everything from one to another. The database being genuinely yours does mean that if you do know Postgres, you can connect to it, query it and back it up on your own schedule.
How your own database worksNo. The testing work is encrypted end to end in your team’s browsers, so your database holds it sealed, and neither what we hold nor what your database holds opens it alone. Beyond that, it is the database that refuses rather than the interface. Every table is protected by row-level security evaluated by Postgres on every query, and every data-access policy also requires a recent second-factor check, so a stale session returns nothing. Resetting a second factor needs an administrator signed in to your own portal, so control of access stays inside your firm.
A compromise of Pental reaches only what runs your account. Your clients, assessments, findings, evidence and reports sit in your own hosting account, and there is no credential on our side that unlocks them.
Another firm using Pental cannot see them either, and that separation is physical rather than a permissions setting: each project signs its own tokens, so a session from one firm does not fail an authorisation check against another, it fails to validate at all.
What a breach of Pental would reachYou decide where it runs. Bring a key for OpenAI, Anthropic or Groq and requests go to your account under your terms. Or run Ollama locally, or any compatible endpoint you host, and nothing leaves your environment.
The key is encrypted on write inside your own database, with a key generated in that same database, and the plaintext column is nulled.
Every generated field has its own editable prompt, with a reset to the default. Configure no provider and the AI is simply absent.
How the AI runs on your keyCompletely. Your domain with TLS issued automatically, your favicon, your login page, your colours for both themes, your fonts, and email from your address through your own relay.
No Pental branding anywhere a client can look, and none where your team looks either.
What white-labelling coversWith an email address and password, then a mandatory second factor: an authenticator app or a passkey, enrolled before the portal opens. Passwords are hashed and stored only in your own database.
The password is also what opens a person’s encrypted work on a new browser, as they sign in, with nothing extra to set up. A forgotten password is reset from the sign-in page, and the work opens again with the new one.
How credentials are handledYes. Findings, evidence, scope, notes, summaries, comments, credentials and every file of an engagement are encrypted in your team’s browsers before they are sent, and opened only in the browsers of the people allowed to read them. Your database keeps sealed values, and nothing it holds opens them by itself, so neither Pental nor whoever hosts the database can read the work from it.
There is nothing to set up: it is on for every firm, each browser gets its keys as its person signs in, and a badge on every engagement says it is encrypted. Client and engagement names, dates, statuses, severities and scores stay readable, so the calendar, counts and dashboards keep working.
How the encryption worksThe Portal is priced per tester, with every feature included. The rate falls with every tester you add, and you add or remove testers whenever you like from your dashboard, pro-rated. The reporting on its own is free: our open-source reporting tool runs on your own server.
The trial is free, with no card required. Its days start when your portal goes live, so setting up uses none of them, a change of testers during it keeps the trial, and if you need longer, ask us. One trial per account.
Cancelling ends the subscription and your access to the software, and nothing else. The project is in your own account, so it carries on exactly as it was, and you can export everything from the portal at any time.
See the pricingBook a live demo, ask about deployment, migration or pricing for a larger team, or ask how a specific part of the architecture works. The engineers who build it answer.
One platform for every engagement your firm runs, end-to-end encrypted on a database your firm owns. Free to try, no card required, and the database stays yours either way.