Today I’m releasing SUNDERKEY 0.1.0 under the Apache License 2.0 license.
SUNDERKEY is a control plane for coordinated, authorized offensive security assessments. Its premise is simple: a complex assessment should not depend on one generalist trying to reason about every system. Narrow specialists should be able to work from a common mission plan, share evidence, hand work to one another, and remain subject to clear authority and independent review.
The name SUNDER stands for Signals Unmasking, Network Discovery, Exploitation, and Reconnaissance.
What the Initial Release Includes
The repository contains 451 role definitions: 391 specialist profiles, 25 domain commanders, and 35 shared roles. They cover areas including web and APIs, identity, cloud, enterprise systems, software supply chains, firmware, cyber-physical systems, and cross-surface patterns. These are definitions of responsibilities and capabilities, not a claim that 451 agents are running autonomously.
The code also includes mission planning and action-governance components, bounded work assignment and handoffs, offline analysis of supplied evidence, and workflows for findings, retesting, and reporting. Its interfaces are designed to keep a specialist’s proposal separate from the authority to act on it.
That separation matters. A plausible attack path is not a verified finding. An old approval is not current authorization. A successful local test is not proof that a live deployment is safe or qualified. SUNDERKEY is being built around those distinctions.
Where the Project Stands
Version 0.1.0 is an early code foundation. It is not a turnkey, production-qualified autonomous penetration testing service. Installing it does not grant access to a target or start an assessment. Live use requires the target owner’s permission, an exact scope, and independently operated and qualified infrastructure for identity, credentials, network egress, containment, monitoring, and target-specific integrations.
The repository includes documentation, schemas, examples, tests, and a Python command-line interface so others can inspect the design and work with its offline components.
License and Participation
SUNDERKEY is copyright 2026 Morgan Bleck and licensed under the Apache License, Version 2.0. The repository contains the license, contribution guidance, and a private vulnerability-reporting route.
I’m releasing this foundation so security practitioners and builders can examine it, challenge its assumptions, and help improve it. If that work interests you, start with the README and architecture documentation. Use the project only for systems you own or are expressly authorized to assess.
Before posting, replace the LinkedIn blog-link placeholder and confirm that the repository is public and the outstanding release reviews have cleared.