Skip to main content

P-BitM documentation

Persistent Browser-In-The-Middle

P-BitM is a containerized platform for controlled Browser-in-the-Middle security assessments. It combines an administrative dashboard, isolated campaign services, dedicated browser containers, live session viewing, and bounded evidence collection.

Use P-BitM only on systems you own or where you have explicit written authorization. Review the authorized-use policy.

See it in action

One focused dashboard for each active session

Review live browser activity, operator controls, screenshots, and bounded evidence from the session detail view.

P-BitM session detail view with live control, screenshot gallery, and evidence panels

Explore live sessions

Understand the operator-facing live view, streaming modes, and evidence behavior.

Watch demos

Browse short recordings of campaigns, extensions, modules, and sessions.

Choose a path

Get to the right answer quickly

Get started

Check requirements, install the platform, and verify the control plane.

Operate campaigns

Prepare resources, launch authorized campaigns, and manage sessions.

Administer

Configure production routing, TLS, storage, backups, and maintenance.

Extend P-BitM

Work within the backend, frontend, database, and extension boundaries.

Deployment flow

From source to a verified stack

Prepare the host

Confirm Docker Engine, Buildx, Compose, Python, networking, and written authorization in the requirements.

Provision P-BitM

Clone the source, create the CLI environment, review config.yaml, and run python3 p-bitm.py setup.

Verify and launch

Resolve doctor failures, start the control plane, and prepare only approved campaign resources and recipients.

Explore by role

Documentation shaped around the work

Campaign workflow

Schedule Complete campaigns, launch Standalone campaigns immediately, and control either type through completion.

Sessions and evidence

Inspect sessions and handle collected records and exports.
This documentation tracks the actively developed P-BitM 0.1.0 codebase. Interfaces and stored data formats may change before the first stable release. Internal HTTP endpoints are not a public compatibility contract.