L1 — Storybook workshop for the design system.
-
Updated
Aug 7, 2026 - TypeScript
L1 — Storybook workshop for the design system.
L1 — shared service scaffolding.
RETIRED 2026-08-07 — the UniERP development monorepo. Superseded by the layered polyrepo at github.com/kannan19302/UniERP. Read-only; history preserved.
L2 — the schema-driven page runtime.
L7 — release-train manifest, shared CI gates, federated ratchet.
L6 — first-party verticals. Depends on nothing but the public API.
L1 — shared TypeScript and Prettier configuration.
L1 — session, token and permission-matching primitives.
L1 — tenancy context, policy engine, audit, outbox, idempotency.
L2 — the capability-scoped V8 isolate extensions run in.
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.
L4 — Tenant Admin Portal and Application Layer.
L3 — the modular monolith. 45 business modules, two routers, one deployable.
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.
L2 — optional Hyperledger Fabric integration.
L7 — compose, Kubernetes, ingress, registry, runbooks.
Superseded by unierp-extensions/real-estate — archived. The four first-party verticals now live in github.com/kannan19302/unierp-extensions under AGPL-3.0.
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."