What We Worked On in January 2026: Launching Neuron

For two years, most of what this team built happened out of sight. January is the month that changed. On January 5 we announced Neuron, and from that day on the work we had been doing quietly became something other teams could see, question and try.

This is the first of a new series on this newsroom: a short monthly look back at what the company worked on. The detailed product stories live on neuron.ws. Here we keep the company view.

Neuron is out in the open

Neuron is a security engagement management platform for teams that run many assessments at once: penetration testing firms, internal security teams, MSSPs and government organizations. It is not a new version of PenTest.WS. It is a ground-up re-architecture, built around the problems we kept seeing as our users’ teams grew past a handful of testers. Reporting that only starts after testing ends. Review that happens in email threads. Clients who have to ask for status updates because there is nowhere else to look.

Our launch announcement on neuron.ws (opens in a new tab) walks through the platform in detail, and the press release covers the company side. The short version: Neuron brings testing notes, findings, quality assurance, reporting and client delivery into one system, and it runs on infrastructure the customer controls. On premises, in a private cloud, or on a network with no internet connection at all.

PenTest.WS is not going anywhere

The question we expected most was whether Neuron meant the end of PenTest.WS. It does not. Hobby and Pro accounts keep working exactly as before, and we remain committed to the operators and small teams who have relied on PenTest.WS for years.

The two products serve different needs. PenTest.WS is the toolkit for an individual operator. Neuron is for organizations where several testers, reviewers and managers touch the same engagement, and where the process around the testing matters as much as the testing itself. Same people behind both.

The library work underneath the launch

Launch weeks are rarely quiet for engineering, and this one was no exception. A lot of January went into the Findings Library, the store of approved finding language that a team reuses from one engagement to the next.

A single vulnerability often needs different wording depending on the kind of assessment it turns up in. The library now holds those versions as separate variants of one finding, each with its own severity and each moving through review and approval on its own. A tester adding a finding to an engagement picks the variant that fits the work, and gets language a reviewer has already signed off. The Findings Library spotlight (opens in a new tab) shows how that reviewed content and Neuron AI work together.

That review step is the same one findings themselves go through. The QA pipeline (opens in a new tab) gives every finding a defined path from draft to approval, with the reviewers and approvers each team chooses, so nothing reaches a client report without sign-off.

Available by private demo

Neuron is available to enterprise customers through a private demo. Because every deployment runs on the customer’s own infrastructure, we prefer to start with a conversation about where it will live and who will use it, rather than a sign-up form.

Read the full product stories at neuron.ws/news (opens in a new tab), or book a Neuron demo (opens in a new tab).