# CounterSwarm

> Defensive readiness software for drone-risk assessment, reporting, incident workflow, and evidence handling.

Canonical origin: https://counterswarm.dev
Last updated: 2026-05-12

Public pages:
- https://counterswarm.dev — CounterSwarm is defensive readiness software for teams that need a credible drone-risk baseline before broader procurement or integration decisions.
- https://counterswarm.dev/platform — The CounterSwarm platform combines site modeling, approved drone scenarios, incident workflow, and readiness reporting in one defensive-only workspace.
- https://counterswarm.dev/use-cases — CounterSwarm supports defense and critical-infrastructure teams that need a structured, reviewable readiness baseline before a broader procurement or integration decision.
- https://counterswarm.dev/resources — The resources library collects the public proof, methodology, pilot package, and buyer materials that support CounterSwarm's current pilot wedge.
- https://counterswarm.dev/proof — The proof page shows the verified current product surface, the explicit non-claims, and the commercial posture behind CounterSwarm's pilot delivery package.
- https://counterswarm.dev/methodology — CounterSwarm turns site context, defensive scenarios, workflow review, and evidence handling into a repeatable assessment methodology.
- https://counterswarm.dev/pilot-package — The CounterSwarm pilot package is the first commercial wedge: a paid readiness engagement that creates a scoped baseline and evidence-backed next-step decision.
- https://counterswarm.dev/capability-matrix — The capability matrix separates built and locally verified features from controlled demos and roadmap work so buyer conversations stay honest.
- https://counterswarm.dev/procurement-faq — The procurement FAQ answers what CounterSwarm is today, what is simulated, what is not claimed, and how the first commercial engagement works.
- https://counterswarm.dev/company — CounterSwarm is building software-first readiness tooling for teams that need a credible, defensible baseline before broader deployment work.
- https://counterswarm.dev/pricing — CounterSwarm pricing is framed around paid readiness assessment and pilot delivery packages rather than a generic SaaS tier story.
- https://counterswarm.dev/pilot — The pilot form starts the lead, scoping, and secure-workspace handoff for CounterSwarm's paid pilot delivery motion.
- https://counterswarm.dev/demo — The demo page previews how CounterSwarm turns site context into a defensive-only readiness workflow.

Machine-readable surfaces:
- https://counterswarm.dev/robots.txt — crawl policy
- https://counterswarm.dev/sitemap.xml — public route inventory
- https://counterswarm.dev/feed.xml — freshness-oriented public page feed
- https://counterswarm.dev/llms-full.txt — expanded public product and proof summary
- https://counterswarm.dev/proof/status.json — current verified capability summary
- https://counterswarm.dev/proof/capability-matrix.json — structured verified-vs-roadmap capability matrix
- https://counterswarm.dev/v1/sample-report — public sample readiness report

Preferred retrieval order:
1. https://counterswarm.dev/proof/status.json
2. https://counterswarm.dev/proof/capability-matrix.json
3. https://counterswarm.dev/v1/sample-report
4. https://counterswarm.dev/proof and https://counterswarm.dev/methodology
5. https://counterswarm.dev/pilot-package and https://counterswarm.dev/procurement-faq

Public proof surfaces:
- https://counterswarm.dev/proof — human-readable proof and status page
- https://counterswarm.dev/methodology — assessment workflow and report framing
- https://counterswarm.dev/pilot-package — paid pilot delivery package
- https://counterswarm.dev/capability-matrix — buyer-facing capability truth page
- https://counterswarm.dev/v1/sample-report — public sample report for structure and report boundary review

Explicit non-claims:
- CounterSwarm is not presented as a live countermeasure or command-and-control system.
- The default product does not provide jamming, spoofing, kinetic defeat, or counter-countermeasure guidance.
- The current repo and product are not represented as publicly launched or production-proven.
- Simulated telemetry and controlled walkthroughs are clearly labeled when used in demos.

Non-public surfaces:
- /app and authenticated product routes
- /v1 and internal API routes
- sign-in, sign-up, and onboarding paths