API design
How the system talks
- REST endpoints namespaced per module behind a single gateway
- Role-scoped access so a warehouse view can't see payroll data, by design
projects / Vertexa-ERP
Modular ERP Platform
One system for HR, inventory, finance, sales, and reporting.
- Next.js
- TypeScript
- Node.js
- MySQL
- 5
- Modules unified
- Real-time
- Cross-department reporting
- Reusable
- Component library across modules
The challenge
Operations were fragmented across spreadsheets and disconnected tools — finance couldn't see inventory in real time, and HR data lived in a separate silo entirely.
The solution
Contributed to a modular ERP system built with Next.js, implementing responsive interfaces and business-focused modules so departments work off one shared source of truth instead of five conflicting ones.
- HR
- Inventory
- Finance
- Sales
- Reports
System design
- FrontendNext.js dashboard, role-based views per department
- API GatewayAuth and request routing per module
- ServicesIndependent services per business module
- DatabaseMySQL with module-scoped schemas
Engineering notes
Performance
What keeps it fast
- Built reusable, maintainable UI components shared across modules to speed up delivery
- Optimized rendering and resolved frontend performance issues through debugging and testing
Challenges
What was hard to get right
- Designing module boundaries that mirror department boundaries, not just code convenience
- Keeping a consistent design system across many independently-built modules
Lessons learned
What I'd carry into the next project
- A shared component library pays for itself fast once you have more than 2-3 modules
- Close collaboration with designers early avoids expensive UI rework later