Built and Tested by Penetration Testers

Pentest Management,
Powered by AI.

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 trial  ·  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.

Watch the full product demo · 9:54, narrated

ReportingFindings drafted from evidence, rendered into your own Word template or the built-in PDF, and read back in after you edit.
Client portalClients sign in on your domain to read findings live as you release them, take delivery and ask for retests.
You own your data, end-to-end encryptedIt lives in your own Postgres database, which Pental has no access to, and the testing work in it is encrypted in your team’s browsers.
QA and moreA review queue with a named sign-off, your clients’ Jira, ServiceNow or GitHub, and automation for the admin.
The Problem

The Way Most Firms Still Deliver.

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.

Messy, manual reportingFindings are written once, from evidence, and rendered into your template the same way every time.
No structured delivery processScope, phases, findings, review, sign-off, release and retest all sit on one engagement record.
Inconsistent QAEvery report goes through the same review queue and your own QA checklist, with comments anchored to the text and a named sign-off.
No central vulnerability libraryA findings library the whole team reuses, scoring and remediation intact, that improves with every edit.
Repetitive adminAttestation letters and vulnerability reports are generated from the engagement rather than retyped from the last one.
A poor client experienceClients get a portal under your brand that stays open between engagements, rather than a PDF in an email.
Client data held by a third partyYou own your data, in your own database, and Pental has no access to it. The testing work in it is also encrypted end to end, so your database’s host holds it only as ciphertext, and nothing in the database opens it by itself.
Reports that read differently by testerOne findings library, and templates that render the same way every time, whoever wrote the findings.
Processes that break as the team growsThe same workflow, templates and review for every tester, however many you have.
Under Your Brand

One Engagement, Start to Finish, With Your Name on It.

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.

01

Your Client Signs In to You

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.

  • Your hostname, with TLS issued automatically
  • Your heading and the line under it, set in Settings
  • Email and password, then a mandatory second factor

Calderwood SecurityWhat their client signs in to

A sign-in page carrying one firm’s logo, colours and wording.
02

Your Team Opens the Work, Not a Folder

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.

  • Assessments by state, with the lead named
  • A QA queue with a count, not a convention
  • The latest findings across every engagement

Calderwood SecurityTheir team

A testing firm’s dashboard: active tests, pending QA, their own and their team’s assessments, and the latest findings by severity.
03

Findings Are Written Once and Released on Purpose

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.

  • Draft until a required field is filled in
  • Client visible is a decision, not an accident
  • Severity colours are yours, carried through to the report

Calderwood SecurityTheir team

A findings table with severity, CVSS, status, and the draft and client-visible switches that decide what a client can see.
04

Your Client Reads It in Your Portal

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.

  • Only what you released, and only their own
  • Remediation progress they can show their board
  • A retest requested with one button

Calderwood SecurityTheir client, signed in

A client’s view of the same portal: their assessments, their open findings and their remediation progress.
05

And the Finding Itself, in Your Words

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.

  • Description, impact, remediation and evidence
  • Every affected asset, not the first three and a count
  • Request a retest from the finding

Calderwood SecurityTheir client, reading a finding

One finding as a client reads it: severity, CVSS, status, description, remediation advice, evidence and the affected assets.
06

A Different Firm. The Same Software.

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.

  • Your palette for light and dark, set separately
  • Critical through informational in your own colours
  • Your fonts for headings, body and code

VantrellTheir team

The same dashboard again, with the theme colours, accent, severity scale and typeface all changed by the firm.
07

And a Third, in the Other Direction

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.

  • Every feature included, all of this too
  • Your colours carried into every email and document
  • Set up in your first week, changed whenever you like

Thornbury CyberTheir team

A findings table with the severity scale repainted in the firm’s own colours.
From Evidence

Rough Notes In. A Finished Finding Out.

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.

Your Own Database

Where Your Data Actually Lives.

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.

Pental's serversAbout your firm
  • Your accountWho you are, your subscription and billing.
  • Your portal's addressYour domain & DNS status.
  • One countHow many testers your portal has.
Nothing your clients trust you with is on this side.

If Pental were breached, your clients' data would not be in it.

See exactly what an attacker would get
The full list is in the privacy policy.
Your Postgres databaseEverything else
ClientsAssessmentsPhasesScopesFindingsEvidenceFilesReportsRetestsUsersSessionsMFA enrolmentsChecklistsLibraryMethodologiesSettingsBrandingTemplatesSecretsand more…
A finding, as your database keeps it
titlepe2e1.4c1f…e09a.kQ3vN8wT…sealed
severityhighreadable
descriptionpe2e1.4c1f…e09a.Zm9yIGVh…sealed
evidencepe2j1.4c1f…e09a.W3sidHlw…sealed
119tables129policies66fields sealed1account, yours

If your own database were breached, the testing work in it would be unreadable.

Read the full architecture
Your account. Your region. Your keys.
Explore

Every Part of It, in Full.

Ten areas, each answering one question properly instead of all of them briefly. Start with the platform, or with the question your firm asks first.

Pricing

Report for Free. The Portal, Priced per Tester.

Report is Pental's reporting on its own, free and open source on your own server. The Portal is all of Pental.

ReportOpen source
Free and open source on GitHub. Your reporting, on your own server.
curl -fsSL https://pental.io/report/install.sh | sh
Free
No card, and no account with us.
Install with one command
Your fields, AI and Word templates
Your server and your database, end-to-end encrypted
As many testers as you like

Pentest 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 Report
Portal
All of Pental, fully white-labelled, priced per tester.
£293.35a month
£58.67 a tester, a month
Free trial  ·  No card required
Client portal with delivery and live reporting
Your own database, end-to-end encrypted, on your own domain and mail server
Additional features: QA, issue trackers, automation and more

Add 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.

Questions

The Things People Actually Ask.

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 platform

Yes. 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 integration

On 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 guide

Your 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 works

No. 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 reach

You 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 key

Completely. 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 covers

With 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 handled

Yes. 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 works

The 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 pricing
Contact

Talk to the People Who Built It.

Book 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.

Emailhello@pental.io
ResponseWithin 24 hours
Live demoAn hour on Microsoft Teams for your own questions and requirements, booked right here

01Choose a DayWeekdays, UK time

02Choose a Time

03Your Details

Pick a time, then add your name, email and company. The invitation arrives the moment you book.

Set It Up Before Your Next Engagement.

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.