Category: Ember BOS · Business Operating System
An ERP that shows where every number came from.
Ember BOS is a China-first ERP and business operating system under staged implementation. The controlled staging surface currently demonstrates finance-led workflows, audit and lineage, documents, approvals and selected reporting. Inventory, CRM, procurement and payroll remain visibly unavailable until their real backends land.
Built for
- Chinese SMEs
- Accountants & finance teams
- Business operators
- Status
- Beta
- Ledger step
- Ledger step 3 of 4
- Family
- Ember family
- Access
- This site only
- Listed
- Last change
- None since listing
- Staged implementation
- Beta
- Accounting spine first
- Finance-led
- Provenance on figures
- Number-level
- Approval boundaries
- Human-gated
See it working
A real capture of the live product, not a mock.
What this page can show today
- The register marks this track as a public test or verification build.
- This track is documented on this site only.
- Capabilities below are the published feature list for this track.
Limits of this page
- No public product site is published for this track.
- Beta is not a production claim.
- This page does not publish financials, headcount, or client names.
Key features
- 01
Accountant-first ledger
Trial balance, sub-ledger, journal entries and close-readiness workflows form the verified accounting spine.
- 02
Number-level provenance
Trust labels and lineage drawers show where figures came from and what evidence supports them.
- 03
Human-gated automation
Material finance, tax and operational actions pass through explicit approval and audit boundaries.
- 04
Connected operating modules
The operating graph is designed to connect finance, tax, documents, inventory, procurement, CRM, payroll and risk. Current staging keeps inventory, procurement, CRM and payroll explicitly unavailable until real backend integration lands.
Published links
Technology stack
React · Fastify · PostgreSQL · TypeScript · Playwright
Related platforms
Family on the register: Ember family Same family first, then tracks at the same lifecycle stage.
Same family · Live
Ember AIFoundation Models
Public product site
Same family · Live
Ember LegalLegal Technology
Invite only
Same family · Beta
Ember LiveReal-Time Model Surface
Invite only
Same family · Beta
Ember DesktopAI Work Operating System
This site only
This cell on the investor register
Status and family write into the /investors URL. The holdings table lists every public track in that cell.
Open Beta Ember family holdingsJSON fields are copied from this row in src/data/platforms.ts. No financials.
How this track works
Audience on the left, the published Ember stack in the middle, capabilities on the right. Every node is copied from this track in the public register.
Inputs
Coreidea and Ember
This track does not name an Ember model on its published stack.
Outputs
Select a node to inspect the published role and capability.
Business software hides where the numbers come from.
Most ERP systems present figures as facts — no trail back to the source document, no record of who approved the entry, no distinction between verified and estimated.
Figures without provenance
A balance sheet number that cannot be traced to its source document is an assertion, not an answer. Auditors, investors and operators need the trail.
Automation without approval
Material finance and tax actions — journal entries, payment runs, tax filings — need explicit human approval. Automation that skips the gate creates liability.
Modules promised, not delivered
ERP vendors sell the full suite and deliver a fraction. Empty modules hide behind the same navigation as working ones — the operator discovers the gap at the worst moment.
Finance first. Honest about the rest.
Ember BOS builds the accounting spine first and marks everything else as unavailable until the real backend exists. No empty modules pretending to work.
Accountant-first ledger
Trial balance, sub-ledger, journal entries and close-readiness workflows form the verified accounting spine — the first thing built, not an afterthought.
Number-level provenance
Trust labels and lineage drawers show where each figure came from and what evidence supports it. Every number has a trail.
Human-gated automation
Material finance, tax and operational actions pass through explicit approval and audit boundaries. The system proposes; the human approves.
Visibly honest staging
Inventory, CRM, procurement and payroll are explicitly marked unavailable in the staging surface. You see what works and what does not — no surprises.
Open the ledger. Trace every number. Approve every action.
Access the staging surface
The controlled staging environment is live. Finance-led workflows, documents and reporting are functional; other modules are visibly marked as pending.
Work the ledger
Create journal entries, review the trial balance and sub-ledger, and run close-readiness workflows. The accounting spine is the first verified module.
Trace provenance
Open the lineage drawer on any figure to see its source, trust label and supporting evidence. No black-box numbers.
Approve material actions
Finance, tax and operational actions above defined thresholds require explicit approval. Every approval is logged with actor and timestamp.
Generate reports
Selected reporting is available in staging. Reports carry the same provenance and approval trail as the underlying ledger.
Built for the audit, not the demo.
React + Fastify stack
React + TypeScript front end, Fastify + PostgreSQL back end. Playwright for end-to-end test coverage. Modern, typed, testable.
Ledger spine
Trial balance, sub-ledger, journal entries and close-readiness workflows. Double-entry accounting with the lineage layer built in, not bolted on.
Lineage drawers
Every figure carries a trust label and a lineage drawer showing its source document, entry path and supporting evidence.
Approval boundary system
Material actions are gated behind explicit approval with logged actor, timestamp and context. The boundary is enforced by the system, not by convention.
Who Ember BOS is built for.
Chinese SMEs
A China-first ERP that starts with the accounting spine and grows module by module — not a Western ERP awkwardly localized.
Accountants & finance teams
Trial balance, sub-ledger, journal entries and close-readiness in one place, with provenance on every figure.
Business operators
Approval boundaries and audit trails on material actions. You know who approved what, when, and with what evidence.
Audit-ready organizations
Number-level provenance and logged approvals mean the audit trail exists before the auditor asks — not assembled after the fact.
Questions, answered.
What does "staged implementation" mean?
Ember BOS is being built module by module, with the accounting spine first. The staging surface shows what is functional and explicitly marks what is not — inventory, CRM, procurement and payroll are visibly unavailable until their real backends land.
Why are some modules unavailable?
Because their real backends do not exist yet. We mark them as unavailable rather than shipping empty screens that pretend to work. When a module lands, it lands with a real backend.
Is it designed for Chinese businesses?
Yes. Ember BOS is China-first: Chinese accounting standards, Chinese tax workflows, Chinese business operating norms. International compatibility is a future track, not the starting point.
How do I get access?
For partnership or early-access conversations, contact info@coreidea.cn.
An ERP that answers "where did this number come from?"
Ember BOS is in staged implementation with the finance-led spine live. Talk to us about early access.