PentestGPT Portal

Portal Login

Launch Wizard

Create Run

Step 1

Pick the assessment template

Choose what you want PentestGPT to do. The portal will apply the right workflow and runtime defaults automatically.

Assessment Template AI Model Choose the model up front so you can compare runs by template and model. Execution Path Choose an Azure worker region, or choose a checked-in LAN relay to route an Azure run through a workstation-local proxy.

Template Summary

Step 2

Set the target

Use a URL, host, or artifact reference as the primary target. Upload evidence only when the template needs files.

Primary Target

Target Provide the authorized target required by the selected assessment.

Optional Evidence Upload

Open this only when the assessment needs a file or artifact reference.

Portal Upload

Upload a file only if this workflow needs artifacts.

Evidence File

Artifact-based templates can use uploaded evidence URLs directly as the target value.

No uploaded evidence yet.

Step 3

Review and launch

Confirm the route, review the run package, and make final operator notes without losing the launch surface.

Run Package

Run Summary

Template, route, model, runtime, and artifact metadata before dispatch.

Edge Readiness

Allowlist Confirmation

Quick verification that the current worker route is allowed through the origin or WAF path.

Operator Overlay

Notes Sent To The LLM

Add scope constraints, credentials, exclusions, or handoff context that should shape the run.

Run Notes And Constraints Use this for scope notes, exclusions, credentials, or target-specific context.

Prompt Surface

Final Prompt Notes Preview

This is the operator-facing note block that will be carried into the final run prompt.

The final prompt preview updates here as you change the template, timeout, and operator notes.

Advanced Controls And Runtime Overrides

Job ID Timeout Seconds Choose a longer runtime for slower or deeper authorized assessments. Execution Profile The selected template controls which runtime profiles are recommended or allowed. Artifact Prefix Correlation ID

At A Glance

Launch Checklist

Documentation

Reports And Exports

No runs yet.

Templates

Prompt Library

Tune built-in prompts, create custom variants, and keep saved overrides in the portal so launch templates stay editable without touching source files.

No templates loaded yet.

Editor

Template Editor

Template ID Label Category Risk Posture Summary Default Timeout Seconds Tools Comma-separated tools shown in the wizard summary.

Prompt Template

Instruction

Child Overlay

Child Instruction Overlay

Structured Operator Inputs

Operator Inputs JSON Optional JSON array defining extra operator prompts shown in the launch wizard. Supported kinds: text, textarea, password.

Target Input Kind Target Input Label Target Placeholder Target Help Suggested Target Value

Runtime Policy

Default Execution Profile Allowed Profiles Execution Rationale

Comparison

Diff Vs Built-In Baseline

Select or edit a built-in template to compare it against its baseline.

Operator Flow

Follow the playbook in three moves

Use the library as a guided sequence: choose the workflow, inspect the exact logic, then preserve findings that should survive the run.

0 Loaded playbooks

0 Steps in selection

0 Retained findings

Browse

Filter by OWASP, phase, or template until the operator sees the right workflow for the run.

Inspect

Read the goal, preconditions, steps, payloads, and evidence contract as one readable sequence.

Retain

Save reusable endpoints, notes, and branch clues so the next operator starts with context instead of rediscovery.

Step 1

Browse Curated Workflow Library

Start with the runbook list. Filter to the OWASP area or phase you need, then pick one workflow to inspect in full.

Find

No playbooks loaded yet.

Step 2

Choose a playbook

Select a playbook from the library to inspect its goal, preconditions, steps, payload templates, and evidence expectations.

Step 3

Promote Findings Into Passive DB

Retained findings now live in the Passive DB workspace. Group URLs by root domain, expand the domain row, and keep the editor focused on the specific result you want to preserve.

Workflow handoff Inspect the playbook here, then open Passive DB to retain or refine the URL-level results tied to that workflow.

Passive DB

Retained Findings By Root Domain

Review the retained URL inventory as a passive database. Each domain row expands into the URLs, notes, and captured results currently attached to that surface.

No retained findings yet.

Editor

Retained Finding

Title Status Endpoint Method Identifier Confidence Playbook ID Template ID OWASP ID Phase Job ID Target

Notes

Artifacts

Attach CSV Or TXT Evidence

Artifact File

Retained findings accept `.csv` and `.txt` artifacts only. Attach endpoint ledgers, route lists, or analyst notes that should stay with this finding.

No artifacts attached yet.

Infrastructure

Workers, Relays, And Control Plane

Mission Control

Operate the platform in a clean 1, 2, 3 flow.

Start with routing and posture, move into cloud worker capacity, then extend operator reach with LAN workers and relay bundles. The page should read top to bottom without forcing you to hunt for the next action.

Read the room

See routing, capacity, LAN health, and control-plane exposure first.

Stage the fleet

Deploy, activate, and inspect Azure regions in one focused area.

Extend operator reach

Manage LAN workers, download bundles, and verify platform support without leaving the page.

Step 1

Snapshot And Routing

Establish the current state before touching regional capacity.

Command Snapshot

Fast read on active routing, ready regions, and operator-side reach.

Azure Worker Control

Deploy, activate, or retire a region without leaving the page.

Azure Region Choose the region you want to stage, activate for new jobs, or remove.

Step 2

Cloud Worker Fleet

Make region status easy to scan before you decide where jobs should route next.

Worker Fleet

Loading regions...

Every supported Azure region stays visible here, including standby capacity that can be deployed on demand.

Step 3

LAN Reach And Support Surface

Keep the operator-side relay path and supporting platform signals together.

LAN Workers

Loading LAN workers...

Checked-in operator machines stay near the top of the page so local reachability is never buried at the bottom.

Recent Executions

LAN Worker Bundle

Generate the next operator package without leaving Mission Control.

Relay Label Embed a recognizable label into the downloaded bundle. Suggested Local Base URL Example: a workstation proxy root like http://127.0.0.1:3000. Package Flavor Pick the operator platform bundle you want to download.

Loading portal session

Create Run

Pick the assessment template

Template Summary

Set the target

Primary Target

LAN HTTPS Relay

Structured Operator Inputs

Origin Access Hints

Portal Upload

Review and launch

Run Summary

Allowlist Confirmation

Notes Sent To The LLM

Final Prompt Notes Preview

Launch Checklist

Reports And Exports

Prompt Library

Template Editor

Prompt Template

Child Overlay

Structured Operator Inputs

Runtime Policy

Diff Vs Built-In Baseline

Follow the playbook in three moves

Browse

Inspect

Retain

Browse Curated Workflow Library

Choose a playbook

Promote Findings Into Passive DB

Retained Findings By Root Domain

Retained Finding

Attach CSV Or TXT Evidence

Job Management Board

Workers, Relays, And Control Plane

Operate the platform in a clean 1, 2, 3 flow.

Read the room

Stage the fleet

Extend operator reach

Snapshot And Routing

Command Snapshot

Azure Worker Control

Cloud Worker Fleet

Worker Fleet

LAN Reach And Support Surface

LAN Workers

Recent Executions

User Management