Introduction
What CS MeshERP keeps, what it never touches, and how the archive, the history and recovery differ.
CS MeshERP is a plug-and-play ERP archive. It connects to your ERP account once, then keeps copies of the records, files and configuration it is allowed to read, and keeps every captured version of them on a timeline you can read back later.
MeshHistory is the application you work in. It is where the captured archive is browsed, searched, compared and exported.
CS MeshERP is in pre-launch. Nothing is purchasable yet and published prices may change before launch. Availability of any individual capability depends on the connector you are on.
What it does
Connect the ERP account once. Records, files and configuration start being captured, with no archive pipeline to build first.
Captured data lands in one archive. Browse it as files, as records, or as a timeline of what moved on a given day.
Each captured change becomes another version on the timeline. Open an earlier one and read it back, and the later versions stay where they are.
Archive, history and recovery are three different things
They are delivered separately and each makes its own promise. Mixing them up is the single most common source of confusion, so the distinction is worth stating plainly.
| Term | What it means |
|---|---|
| Archive | The retained copy of the data. |
| History | The timeline of captured versions over that copy. |
| Recovery | Putting something back. |
The archive and its history are what MeshHistory shows you today. Recovery of a version back into live production is a separate concern and is not part of the archive itself.
What it never does
Archive, history and read-only SQL access do not write back to the ERP. Nothing you do in MeshHistory changes a record in the source system.
Two-way sync between platforms is a separate product with its own rules and approvals. It is not part of what the archive does.
What can be captured
Coverage is not the same everywhere. What a connector can reach depends on four things:
- The ERP and the connector itself
- The permissions on the ERP identity you authorize
- What the source system actually exposes
- What you chose to capture during onboarding
A connector reads the records, files, configuration and source history that the authorized identity is allowed to read, and nothing beyond it. If a rule in the source cannot be represented on the archive side, it is denied or narrowed rather than quietly widened.