Choosing modules
Laraplate is a set of modules on one shared foundation. Core is always there; every other module is optional and declares what it needs in its module.json.
How they depend on each other
| Module | Needs |
|---|---|
| Core | nothing |
| CMS | Core |
| AI | Core |
| CRM | Core |
| SAO | Core |
| ERP | Core, CRM |
| MES | ERP |
| Shop | Core, CMS, ERP, SAO |
All modules share one database schema. Table names carry the module name as a prefix.
Enable a module and the ones it needs, nothing more. For example, a content site needs Core and CMS. A workshop that tracks production needs MES, which brings ERP and CRM with it.
LaraCore
Laraplate Core module: users, ACL, settings, CRUD API, search, versioning and the shared services every other module builds on.
LaraAI
Laraplate AI module: embeddings, vector search, automatic translation, moderation and an in-app assistant.
LaraCMS
Laraplate CMS module: contents, categories, tags, moderated comments, presets and multilingual publishing.
LaraCRM
Laraplate CRM module: counterparties, contacts, leads and opportunities.
LaraERP
Laraplate ERP module: multi-company accounting, sales, purchases, invoicing, inventory and projects.
LaraMES
Laraplate MES module: work orders, routings, shop-floor events, traceability, quality and KPIs.
LaraSAO
SAO (Simply Another Orchestrator): ticketing that correlates code, errors and work, with issue tracker, VCS and log integrations.
LaraShop
Laraplate Shop module: an online sales channel built on CMS content, ERP items and SAO support.