Riven ERP
Live551 modules across 31 companies on one deployment. The system of record that Commerce, Mail, and the Business Suite all read from.
Riven ERP is the ledger and master-data layer underneath everything commercial. It runs 551 modules serving 31 companies on a single self-hosted deployment — one database, one chart of accounts structure, one customer master, with company-level isolation enforced above it.
Shape of the deployment#
| Dimension | Value | Meaning |
|---|---|---|
| Modules | 551 | Installed functional units — accounting, inventory, manufacturing, HR, project, and the connectors between them |
| Companies | 31 | Legal entities with their own books, sharing master data where configured |
| Deployment | Single stack | Runs on Docker Swarm alongside the rest of the platform |
| Consolidation | Group-level | Inter-company transactions eliminate at the group boundary |
Module families#
- Financial — general ledger, receivables, payables, tax, fixed assets, and multi-currency revaluation.
- Supply — purchasing, inventory, warehouse locations, lot and serial tracking, replenishment rules.
- Sales — quotations, orders, pricelists, and the account-level pricing that Riven Commerce resolves against.
- Manufacturing — bills of material, routings, and the work orders that configurable products generate.
- Project and service — timesheets, job costing, and field service scheduling.
- People — employee records, leave, and payroll interfaces.
- Platform — the integration modules that expose ERP data to the rest of Riven.
How other products use it#
ERP is authoritative. Other surfaces read from it and write back through it rather than keeping their own copies.
| Consumer | Reads | Writes |
|---|---|---|
| Riven Commerce | Catalog, stock, account pricing | Orders, quotes, shipments |
| Riven Mail | Contact and account records | Logged correspondence |
| Riven Contact Graph | Customer and supplier master | Relationship edges |
| Riven Deliverables | Document data | — (render only) |
| Riven Pricing Brain | Cost basis | Metered usage journal entries |
ERP is not exposed on the public API. Model-driven workflows reach it through Riven Cortex tools that carry the calling user’s company scope, so a request cannot read another company’s books.
AI against the ledger#
Analysis workloads run read-only. A model can reconcile, summarise, or explain a variance; posting a journal entry remains a human action with an approval trail. Anything that touches the books is recorded in Riven Telemetry with the actor and the prompt that produced it.