Community vs Pro

Community is the free, Apache 2.0 Opcodex core. Pro is planned as proprietary extensions compiled against Community. The dependency direction is Pro → Community; installing or building Community must not require Pro.

Availability

The Pro entries below describe planned scope, not shipped capabilities. Indicative annual pricing is about $149/year for Pro and $749/year for Enterprise, billed annually. License scope, updates, support terms, model limits, supported-client matrix and delivery date remain unconfirmed. Check Pricing and release notes for updates.

Capability	Community	Pro
Ghidra-based disassembly and decompilation	Core foundation	Uses Community
Program databases, loaders, processor support	Core foundation	Uses Community
Local scripts and compatible extensions	Core foundation	Uses Community
Decompiler cleanup	—	Planned extension
C-to-language conversion	—	Planned extension
Source skeleton export	—	Planned extension
Vulnerability pattern scanning	—	Planned extension
Automated triage reports	—	Planned extension
MCP server / agent mode	—	Planned extension

Privacy boundary

Opcodex’s project policy is local-first. Sending binaries or analysis data to a cloud service requires explicit opt-in. Each feature must document exactly what it sends, to which provider, and when. A local model is not automatically offline if its host or plugins can contact the network.

Compatibility boundary

An extension must declare the Community build it supports. Projects should remain useful without a paid extension installed. VERIFY actual extension compatibility, license terms, and data handling before enabling a released Pro feature.

Read the FAQ or browse baseline workflows.