Roadmap

A roadmap of bets. Each test is a bar to clear, not a promise — clearing it triggers the next move (raise / double down); missing it is data. The dream numbers are the north star the tests walk toward, not the bar.

1. Cloud — free + pro (now)

Objective: turn adoption into first revenue and the leads that become enterprise.

What: open any binary (Mac/Linux/Windows) — behavior, capabilities, what it talks to, functions, libraries, memory segments. Pro adds a private workspace + retained history.

Test: do they come, and do they pay? First paying Pro at $149/mo — 100 the bar, 1,000 the dream.

2. Firmware — unpack, inventory, diff (partial)

Objective: own the question "what's inside this firmware / OS / package, and what changed."

What: unpack any firmware, OS release, or vendor package — every binary inside, its SBOM, known CVEs; track which file belongs to which version, then batch-diff and roll up what changed across releases, down to function code.

Test: does someone pay for a firmware/package report? First firmware design partner or first paid report.

3. Audit — malware + vulnerabilities (partial)

Objective: make the findings trustworthy enough to sell as paid audits.

What: malware verdict + CWE vulnerability findings on a binary or firmware; grow the CWE rule set; LLM-triage findings to strip false positives.

Test: are the findings clean enough to bill? First paid audit engagement.

4. Agent — talk to your binaries (partial)

Objective: be the binary-intelligence layer LLMs and agents reason over.

What: MCP server + chat — ask a binary what it does, drive deeper queries, talk to the reconstructed program; structured facts built for agents.

Test: does an agentic workflow actually use it? First LLM-native partner or integration live.

5. Fleet — index the organization (partial)

Objective: turn Pro users and design partners into org-wide deployments — the enterprise revenue.

What: index every binary across all hosts; what's installed where; CVE-vs-SBOM to show what's vulnerable and where; where a hash or similar binary has shown up; malicious indicators.

Test: will an org deploy it fleet-wide and pay? First enterprise contract ($25K+) — one named org indexed across hundreds of hosts.

Ongoing (not a milestone): library / FLIRT / SBOM enrichment — spot more components inside binaries and packages.