Axiom-Trace
Your operations, executed exactly as you designed them — on site, even without internet. Every step recorded, every exception stopped.
A node at each site. A control tower in the cloud. Proof in between.
IN_ATTESA—ax_lottiIN_CODA—0/40IN_CODA_QC——The execution protocol, on every action: who you are → not a duplicate → your role allows it → the step is legal → the rules hold → the write is sealed. Six checks in fixed order — if one fails, nothing is written.
The process runs as you defined it — or it doesn't run at all
That is the whole promise behind the synoptic above. No silent workarounds, no unrecorded exceptions, no "we'll fix it in the report".
Mistakes are caught, not found later
Every action is checked against your rules before it is written down. What doesn't pass, never happened.
Non-conforming work stops here
Out of tolerance? The step is refused and the lot diverted — and the attempt stays on record anyway.
Always audit-ready
Who did what, where and when: a sealed record you can put in front of any auditor — or customer.
No internet? Work goes on
Each site runs autonomously. Everything reaches the cloud when the connection returns — nothing lost, nothing duplicated.
Axiom-Trace Edge
Edge is the software that runs at each site — on a small industrial PC — and executes your operating rules exactly, online or offline. The rules live in a signed file, the manifest: when they change, you ship a new file — not a new installation.
Your rules, in writing
Operating rules live in a signed file (LayoutManifest). New rules? A new version of the file — no reinstall, no downtime.
One action, one write
Identity, permission, rules, workflow step and data are validated together in a single indivisible write — the 5 engines declared in the manifest.
Works offline
Login, actions and records run autonomously: network down, work goes on.
Nothing is rewritten
Every action is appended to a sealed history — alter one record and the chain breaks for whoever checks (SHA-256 hash chain).
Nothing is lost
What happened on site queues in order and syncs to the cloud with automatic retries (CDC outbox).
One product, many trades
The same software runs production, logistics, field service, retail — only the manifest changes (profiles).
Axiom-Trace Control Plane
The Control Plane is the control tower in the cloud: it distributes rules and licenses, watches every site, manages contracts and billing — while sites stay autonomous.
Installed in minutes
A one-time code: plug in the node, it introduces itself and receives its own identity (bt_* claim).
Billing built in
Subscriptions and invoices through Stripe, tied to each company's actual contract state.
Metering on real data
Volumes and limits measured on what sites actually synced — never estimates.
Every site at a glance
Each node reports in at every sync: online, late or offline is always visible (heartbeat).
Licenses that enforce themselves
Signed licenses reach the node; past the grace period only new work pauses — history stays readable (Ed25519).
Many companies, one tower
Different businesses and trades on the same control plane, each isolated at database level (RLS).
Axiom-Trace Trust Protocol
The Trust Protocol is the set of signed proofs exchanged between sites and cloud: sealed records, signed rules, verifiable events — trust you can check, not assume.
Signed rules and licenses
Everything the tower ships is signed; the node verifies the signature before running it (Ed25519).
Tamper-evident history
Records are chained: change one and every record after it shows the break (SHA-256).
Live telemetry
Metrics, site heartbeat and readiness probes in real time (Prometheus /metrics).
If in doubt, it refuses
Requests outside the rules are blocked — not patched later (fail-closed).
Grace, then recovery
If the cloud is unreachable, paying customers keep working; reactivation is automatic (grace period).
Every admin move traced
Portal and operations actions land in the same sealed history (admin audit).
Data Residency & Security
Data stays where your applications generate it: on the edge node, on the customer's premises. The cloud only receives what governance and synchronization need, over TLS channels.
Isolation enforced by the database
Each company's rows are walled off by the database itself — not by application code (PostgreSQL RLS).
Data sovereignty
The edge runs on-premise on your hardware; the Control Plane on a VPS you control. Your data stays yours.
TLS & protected secrets
TLS on every edge ↔ cloud channel, credentials persisted with restrictive permissions, no secrets in the repository.
Privacy by design
Strict per-tenant separation, data minimization toward the cloud, and an audit trail for reporting.
Your data stays yours.
Your edge stays autonomous.
Every operation stays verifiable.
Pricing
A transparent model that scales with edge nodes and managed event volume, without surprises or hidden costs.
Transparent pricing.
No hidden fees.
Scale only when you grow.
Scalability
A natively multi-tenant architecture: from a single pilot site to a distributed edge fleet, without ever changing platform.
Growth without rebuilds
New companies and divisions are new rows in the tower, not new infrastructure.
Runs on small hardware
The same software runs on field mini PCs and site servers: one container, one database.
Multi-site
Multiple sites per company, each with its own autonomous node and identity.
Proven under load
20 VU × 10 min load test: 21,500+ actions, 0 errors, p95 of 233 ms, zero dead-letter.
Start small.
Scale globally.
Same platform, same proof.