The tool that did not exist.
Development begins. A pentester studying for the OSCP builds the tool the job needed.
Since 2017, PenTest.WS has built enterprise software for offensive security teams, deployed entirely on infrastructure you control.
In July 2017, I was studying for the OSCP and went looking for a purpose-built tool to organize a penetration test. There wasn't one. So I built it. Everything we have shipped since answers a problem we have hit in the field.
PenTest.WS LLC
2017, Colorado
Privately held.
No outside investors.
Denver, Colorado
Development begins. A pentester studying for the OSCP builds the tool the job needed.
PenTest.WS LLC is formed in March 2018. The private beta opens to working testers.
Pro launches: offline and self-hosted, for testers under strict NDA. Our sovereignty stance starts here.
A findings system, a DOCX reporting engine, shared engagements and a REST API.
Engagements grow to tens of thousands of hosts. The platform keeps up.
Social engineering, an events timeline, findings groups, reporting briefs and file shares.
January: the offensive security execution platform. March: Burp Suite integration. October: pentest.ws becomes our corporate home.
More products are in development, shaped the same way: from problems we hit in the field, for teams who run them on their own infrastructure.
Follow the newsroomEvery feature started as a problem we hit on a real engagement. We design around the work as it happens: scoping, testing, QA, the report and the retest.
Built for operators first, by people who have run the engagement themselves.
Findings library, multi-stage QA and private AI drafting, because the deliverable is what your client pays for.
On-premises, private cloud or air-gapped. Even the AI. We never hold your engagement data.
From a single operator to global programs, with tens of thousands of hosts per engagement.
Neuron is the offensive security execution platform. Plan, execute, review and deliver every engagement in one place, on infrastructure you own.
Explore Neuron (opens in a new tab)

A real engagement has five stages. We have run every one of them, so the software follows the same order the work does.
Engagements, schedules, assets and credentials, set up the way a lead actually scopes a test.
Playbooks, checklists and AD and Entra attack paths, kept beside the operator while the work happens.
A multi-stage QA pipeline, because every finding should be checked before a client reads it.
A findings library and private AI drafting on your hardware, because the report is the deliverable.
Retests tracked against the original findings, so closing the loop is part of the engagement.
Tell us about your team and environment. We will show you Neuron running the way you would run it: on your infrastructure, under your control.
A person on our team, not an autoresponder.
Your team, your environment, your constraints.
Neuron shown the way you would deploy it.