Thirty products that behave like one
Splitting an ERP into 30 services is only an improvement if they stay coherent. Four shared foundations do that work.
Organization Overview
Aug 2026- 8 teams with no manager
- 4 vacancies open past 60 days
- 2 reorgs awaiting approval
One organisation model
Legal entities, departments, locations and reporting lines are defined once in the Organization module. Every other module resolves against that tree, which is why a payroll cost centre and a project cost centre mean the same thing.
A service per module
Each module is its own deployment with its own database, its own release cadence and its own address. A busy month in Billing has no effect on Recruitment, and rolling one back does not roll back the rest.
A shared shell
Navigation, tables, forms and the module switcher come from one design system. Someone who has learned Attendance already knows how to use Procurement.
Audit built in, not added on
Every module writes to the same audit model: who changed what, when, and from where. It is the same shape in all thirty, so evidence collection is one query rather than thirty exports.
The short version
- Runtime
- Cloudflare Workers, deployed at the edge
- Data
- One database per module, org-scoped from the first row
- Files
- Object storage for documents and evidence
- Access
- REST API and a typed SDK per module
- Addressing
- module.easymanagex.com, one hostname each
- Rollout
- Enable modules one at a time, in any order