Leecycle

Businesses in different industries need CRM, fleet, learning, billing and governance in one system, while every tenant, branch, team and field stays behind access rules that can be audited.

A modular ERP built on shared foundations — tenant registry, organisation profile and hierarchy, roles, an ABAC policy engine, data scopes with row-level security, field-level security and audit logs — with each business module built on top rather than beside them.

• pnpm + Turbo monorepo: a Node/Express API and multiple Next.js "zone" apps behind one shell
• PostgreSQL as the source of truth; row-level data scopes and field-level security
• ACM: permissions compiled per subject (role, team, department, service account…) instead of per user × resource
• Tiered permission resolution ending in default deny; pattern-based policies like module.finance.*
• Audit & access logs, approval matrix, document numbering, currencies & FX as platform services

• Per-user × per-resource permission rows grow multiplicatively; the access model had to compile permissions per subject to stay small and fast.
• Keeping the core industry-agnostic while CRM, fleet and LMS each pull it toward their own shape.

what you personally designed, built or owned on Leecycle

outcomes you can state — adoption, modules shipped, performance you measured