L2 — the schema-driven page runtime.
-
Updated
Aug 7, 2026 - TypeScript
L2 — the schema-driven page runtime.
L6 — first-party verticals. Depends on nothing but the public API.
L1 — Storybook workshop for the design system.
L1 — shared service scaffolding.
L1 — shared TypeScript and Prettier configuration.
RETIRED 2026-08-07 — the UniERP development monorepo. Superseded by the layered polyrepo at github.com/kannan19302/UniERP. Read-only; history preserved.
L2 — the capability-scoped V8 isolate extensions run in.
L4 — Platform Admin Console. Separate origin, realm and ingress.
L3 — identity provider. Separate realm per plane.
L2 — Prisma schema, migrations, RLS policies, isolation-test generator.
Superseded by unierp-extensions/field-service — archived. The four first-party verticals now live in github.com/kannan19302/unierp-extensions under AGPL-3.0.
L1 — the UniERP design system: tokens, components, charts, data grid.
L4 — the developer platform: App Studio, builders, CMS.
UniERP — an open-source, self-hostable multi-tenant application platform that ships an ERP as its first-party app suite.
L1 — the typed, tenant-aware client. Generated from the contracts.
L1 — tenancy context, policy engine, audit, outbox, idempotency.
L1 — session, token and permission-matching primitives.
L2 — optional Hyperledger Fabric integration.
L7 — compose, Kubernetes, ingress, registry, runbooks.
L4 — Tenant Admin Portal and Application Layer.
Add a description, image, and links to the unierp topic page so that developers can more easily learn about it.
To associate your repository with the unierp topic, visit your repo's landing page and select "manage topics."