APPROACH
Four architectural decisions, and what they cost.
A maintenance platform is judged less on its features than on the constraints it accepts. Here are the four Envergure has taken on, the real state of each, and the doors they close.
Four technical invariants
These are architectural decisions, not intentions: each one constrains the data model and closes options. Three hold today; the fourth is stated for what it is.
- 01Holds
Federation before cloud
An instance is complete: it holds its own reference data, stock and maintenance, and runs with no link to the outside. No part of the product requires an online service. Automatic resynchronisation between instances is still to be written.
- 02Holds
Compliance in the model
Specifications that are covered sit in the data schema, not in an export layer. Three of the six S-Series so far — the detail is on the Compliance page.
- 03Holds
Immutable audit trail
Every audited write carries the fingerprint of the one before. The chain verifies end to end, per instance: after-the-fact alteration is not guessed at, it is demonstrated.
- 04Planned
Structural IoT
The aim is for a sensor signature to raise a work order inside the same data graph, with no bolted-on dashboard. Neither the ingestion chain nor the time-series store exists today.
What these choices cost
An invariant that costs nothing is not one. These close doors, and it is better to know before than after.
- No managed service: operations stay with the operator, along with backups and monitoring.
- No third-party online component — no remote fonts, maps or analytics — so a few conveniences are missing.
- A data model constrained by specifications takes longer to change than a free-form schema.
- An append-only journal cannot be corrected: a mistake is undone by a further entry, never by a rewrite.
NEXT STEPS
Let's see how it fits your constraints.
A 90-minute demo over video: product walkthrough, technical Q&A, review of your constraints. Tell us your context and we will tailor the session to it.
Or write to us directlycontact@envergure.cloud