Add capability without rebuilding the core.

A module is a self-contained unit of functionality: it has its own data model, its own business logic, its own interface, and its own permissions. The core platform manages when modules are active and who can access them — the modules themselves don't need to know about each other.

Modules are activated per organization — one client might have CRM and Invoicing active, another might have Documentation and Approvals. Activating a module makes it available immediately; deactivating it removes it from the interface without deleting the data. Organizations grow the system as they need to.

Modules do not share internal state. They communicate through defined interfaces — events, service calls, shared data contracts — not by directly accessing each other's internals. This means a bug in one module cannot corrupt another, and a module can be updated without understanding the entire system.

Modules are versioned independently. An update to the Invoicing module doesn't require touching the CRM module. Updates are tested against the platform interfaces and deployed through the platform's update infrastructure — so clients receive improvements without downtime or manual intervention.