Pressofusione
The die-casting production vertical: genealogy from raw material to lot, quality dispositions, integrity gate. Runs inside your own IT — Docker and PostgreSQL, signed and sealed runtime.
PricingEvery piece knows where it comes from
Material batch → melt → injection cycle → cavity → product → lot. Forward and reverse traceability resolve to the same production context: pick any product and walk back to the batch, the furnace, the machine and the shift.
A lot closes only if it can prove itself
Lot closure is a deterministic gate, not a status flag: sessions closed, melts concluded, quantities reconciled (expected = actual), products dispositioned, non-conformities managed, audit chain valid. If anything fails, the lot is BLOCKED — with the explicit list of reasons.
Tamper-evident, enforced by the database
Every domain fact is appended to a SHA-256 hash chain in the same transaction that records it. UPDATE and DELETE on the event log are rejected by a database trigger — for every role, including the owner. Any restored backup can be re-verified independently.
The UI follows the process, not the tables
Operator: what to do now — session, melt, injection, result. Supervisor: quality dispositions, non-conformities, the integrity gate. Management: KPIs with formal definitions and drill-down into the underlying facts. The interface renders decisions already made by the domain — it never recalculates them.
Acceptance you can execute
Delivery is an Ed25519-signed binary release, with the acceptance toolkit alongside. Collaudo is executable: smoke.mjs walks a full production cycle through the API, verify.mjs proves the audit chain on any database — including your restored backups. The system doesn't ask for trust; it produces evidence.
Perpetual license, per site
One-off setup per node: signed binary license, yours forever. Light service subscription — without renewal the node stays fully operational.
One-off for the node.
A light subscription for the cloud.
The node stays yours — forever.
Local audit today, external notarization tomorrow
The event outbox is already written in an Axiom-Trace-compatible shape: when you need third-party-verifiable evidence, the signed sync channel to the Axiom-Trace Control Plane can be enabled by configuration — it's not required, not included, and off by default. Until then the UI honestly reports CLOUD: NOT CONNECTED.
Axiom-Trace Trust Protocol