Metadata-driven documents
Runtime drives draft create and update, posting, unposting, reposting, derivation entry points, relationship graph loading, and UI-effects shaping through one shared document model.
Build serious business software on a platform designed for documents, reporting, and durable business truth.
NGB Platform is a reusable ERP foundation for accounting-centric business applications on .NET and PostgreSQL. It gives teams metadata-driven documents, runtime orchestration, provider-backed reporting, append-only effects, and clean vertical extensions without falling back to generic CRUD.
Metadata-driven documents Canonical + composable reporting Append-only effects and audit history
.NET + PostgreSQL Platform foundation and durable system of record
Documents + reporting Runtime orchestration, drilldowns, exports, and UI-ready responses
API / Background Jobs / Watchdog Distinct operational hosts on the same platform core
3 live vertical demos Property Management, Trade, and Agency Billing
Platform
Built for the parts generic frameworks leave to every project.
NGB Platform is designed for systems where business documents, posting, reporting, auditability, and long-lived vertical extensions should be platform concerns, not one-off implementation chores.
Canonical and composable reporting
NGB supports fixed business reports such as Receivables Aging or Open Items and flexible dataset-driven reports in the same reporting architecture.
Append-only business truth
Accounting, Operational Registers, Reference Registers, and Audit Log follow durable fact, reversal, and superseding flows instead of silent in-place mutation.
Explicit operational hosts
API, Background Jobs, Watchdog are first-class application hosts built on the same platform core rather than side utilities bolted on later.
What is already present
The docs describe a platform foundation that already covers the hard parts.
- Shared contracts, metadata, definitions, and platform primitives
- Universal catalog and document patterns
- Runtime orchestration for CRUD, lifecycle, posting, reporting, and drilldowns
- Provider-backed PostgreSQL persistence and report execution
- Keycloak-based SSO with separate clients for API, web, background jobs, watchdog, and tester
- Shared Vue UI workspace plus three live vertical demos
ERP foundation
For teams searching beyond a generic ERP package.
NGB fits the open-source ERP framework space when the goal is to build durable, accounting-centric business applications on .NET and PostgreSQL rather than install a one-size-fits-all ERP clone.
Open-source ERP foundation
NGB is not a generic ERP clone. It gives engineering teams the reusable platform layer for ERP-style vertical systems where documents, posting, reporting, and auditability must stay coherent.
.NET ERP platform architecture
The core is built around .NET hosts, runtime orchestration, provider-backed PostgreSQL persistence, and shared UI patterns instead of one monolithic application shape.
Vertical business applications
Property Management, Trade, and Agency Billing show how the same accounting-centric framework can support different domains without rewriting the platform backbone.
Demos
Three live verticals. One shared platform model.
Property Management, Trade, and Agency Billing prove reuse across domains.
Live vertical demo
Property Management
Lease-centric operations
Property Management shows portfolio health, receivables, charges, allocations, reconciliation, maintenance requests, work orders, and completions on the same shared platform backbone.
PortfolioReceivablesMaintenance
- Portfolio KPIs, occupancy, open AR, collected vs billed, vacant units, and overdue work orders
- Receivables workflows such as open items, rent charges, payments, returned payments, credit memos, allocations, and aging
- Maintenance requests, work orders, and completions in the same vertical workspace
- Built on the same runtime, PostgreSQL, reporting, and SSO model as the other demos
Architecture
Hosts stay thin. Runtime stays central. Business truth stays durable.
The host composition, runtime, reporting, and PostgreSQL docs all point to the same structure: hosts compose the platform, runtime orchestrates behavior, provider layers execute concrete reads and writes, and vertical modules add business meaning without leaking into the shared core.
API host
A vertical API host uses the reusable NGB.Api surface, registers AddNgbRuntime(), AddNgbPostgres(connectionString), adds vertical modules, then maps controllers, auth, and health checks.
Runtime
NGB.Runtime is the orchestration center for document workflow, reporting flow, validation, planning, response shaping, and other provider-agnostic execution concerns.
Reporting pipeline
ReportEngine and ReportExecutionPlanner resolve report definitions, effective layouts, filters, plans, and executor paths for both canonical and composable reporting.
Business effect engines
Accounting handles ledger semantics, Operational Registers track movement-based state such as stock or settlements, and Reference Registers model effective facts such as prices or rates.
PostgreSQL provider
NGB.PostgreSql supplies the concrete provider implementation for persistence, dataset bindings, SQL generation, execution, migrations, and report reads.
Operational hosts
Background Jobs, Watchdog remain separate surfaces for scheduling, operability, and schema flow, while still calling into the same platform-safe runtime behavior.
Hosts compose, libraries execute
The host composition docs make the rule explicit: the host is the composition root, while business execution lives in runtime, engines, and provider layers.
PostgreSQL is the system of record
The docs repeatedly frame PostgreSQL as the durable source of business truth, with performance-sensitive reads shaped in backend services rather than UI fanout.
Auditability stays platform-wide
Audit Log records business actions, actor identity, timestamps, and old/new diffs so explainability works consistently across catalogs, documents, workflows, and administrative changes.
Open Source
Inspect the repository, run the documented stack, and extend the platform yourself.
NGB is open and legible: repository structure, runbooks, architecture docs, live demos, and extension guidance are all part of the evaluation path.
Monorepo shape
Platform modules, vertical solutions, shared UI packages, Docker assets, documentation, and tests live in one repository so the architecture stays inspectable end to end.
What to read first
The docs recommend reading vertical definitions, runtime orchestration, posting and reporting logic, PostgreSQL implementation, and then UI behavior in that order.
Run locally
The docs include both Docker Compose and manual runbook paths, covering PostgreSQL, Keycloak, Migrator, API host, Background Jobs, Watchdog, and the web client.
Apache 2.0
The repository README explains the license choice directly: easy to adopt, easy to evaluate, and practical for real engineering teams, including commercial use and modification.