Flyto2 Docs is the public technical documentation and citation surface for Flyto2 Warroom, evidence-backed CTEM, attack surface management, code intelligence, dark web and threat intelligence, automated security testing, red-team workflows, MCP security, scoring, reports, and the deterministic execution engine.
Read online:
- Website: https://docs.flyto2.com
- Product site: https://flyto2.com
- Self-hosted CE: https://docs.flyto2.com/warroom/self-hosted-ce
- GitHub CE: https://github.com/flytohub/flyto-warroom
- Docker Hub CE: https://hub.docker.com/r/chesterhsu/flyto-warroom
| Area | Purpose |
|---|---|
warroom/ |
Warroom, CTEM, surfaces, scoring, BYO integrations, CE install, and APIs |
core/ |
Deterministic execution, evidence replay, and runtime architecture |
modules/ |
Flyto module reference generated from flyto-core |
mcp/ |
MCP server setup and transport reference |
indexer/ |
flyto-indexer code intelligence and MCP tools |
ai/ |
flyto-ai providers, agents, prompts, and CLI |
blueprint/ |
Workflow blueprint docs |
public/llms*.txt |
AI/search-readable citation indexes |
npm installnpm run docs:dev # local VitePress dev server
npm run verify # public docs audit + build
npm run docs:preview # preview built sitenpm run verify runs the public docs audit and VitePress build. The audit
checks the self-hosted CE entry, sidebar, GitHub/Docker links, and AI-readable
llms files so docs, landing, GitHub, and Docker Hub stay aligned.
Docs are the technical source of truth. Use flyto2.com for product
positioning, docs.flyto2.com for mechanics and contracts, and
blog.flyto2.com for educational explanations.
When adding public pages, update:
- VitePress navigation/sidebar when the page should be discoverable;
public/llms.txtandpublic/llms-full.txtfor AI/search citation;- related landing/blog references when the page changes product positioning;
scripts/audit-docs-public.mjswhen a new launch-critical route becomes mandatory.
Small typo and clarity fixes can go directly through a pull request. Larger structural changes should keep docs, landing, blog, GitHub, and Docker Hub wording consistent. Do not publish credentials, customer data, private implementation details, or unreleased customer claims.