RTFMv2 Is Now CoordOps: A Red Team Platform Built for Real Operations

RTFMv2 is now CoordOps.

The new name reflects what the platform has become. What began as a practical toolkit for penetration testers has grown into a connected environment for planning, executing, documenting, and reporting red team operations.

Why the name changed

RTFMv2 was built to help security professionals keep technical knowledge, commands, findings, and engagement data close at hand. As the platform expanded, the work it supported became broader: coordinating operators, organizing sessions, launching tools, preserving evidence, managing findings, and turning technical activity into reproducible reports.

CoordOps—short for coordinated operations—better describes that mission. The name is new, but the product lineage continues: RTFMv2 is now CoordOps.

A red team platform, not another AI-driven vulnerability scanner

The security market is full of products that describe themselves as AI-powered scanners. Their primary output is usually another list of alerts for someone else to validate, prioritize, and translate into action.

CoordOps is built around the engagement, not the alert queue. It is a red team platform for the people conducting the work. It helps operators coordinate methodology, tools, targets, evidence, findings, and reporting while keeping human judgment at the center of every decision.

CoordOps does not claim that AI can replace an experienced penetration tester or red team operator. It does not turn a scan into a red team operation simply by adding an AI label.

What CoordOps brings together

• Session-centered operations that keep scope, targets, credentials, notes, commands, and results associated with the correct engagement.
• Repeatable methodology through customizable checklists, operational guidance, and evidence attached to the work that produced it.
• Tool and workflow orchestration across Windows and Linux systems, including extensible command templates and Node-RED automation.
• Evidence and findings management that connects technical output, analyst notes, assets, vulnerabilities, and supporting artifacts.
• Collaboration and auditability so teams can share engagement context while preserving commands, timestamps, outputs, and decisions.
• Reporting workflows that turn validated operator work into useful technical and executive deliverables.

Where AI fits

AI is a capability inside CoordOps, not the product’s identity. Operators can use it to assist with research, explain technical context, summarize evidence, and accelerate report drafting. CoordOps supports cloud and local model options so teams can choose the workflow that fits their security and privacy requirements.

AI-generated material remains part of an operator-controlled process. It can be reviewed, corrected, traced, or ignored. Scope decisions, exploit validation, risk judgment, and final reporting remain with the professionals responsible for the engagement.

What this means for RTFMv2 users

CoordOps continues the work started by RTFMv2 while giving the platform a name that matches its direction. The focus remains practical: help offensive security teams spend less time reconstructing context and more time performing, validating, and communicating meaningful security work.

Built for the work between the scan and the report

Scanning can identify possible weaknesses, but a real red team operation requires planning, judgment, execution, evidence, collaboration, and clear communication. CoordOps is designed for that entire operational path.

Explore the CoordOps platform capabilities or download CoordOps to see how the red team platform supports real engagements.