New: prepared statements, UPDATE and DELETE, and key lookups that seek — 0.143 ms through the gateway.Read the update

Use case · Manufacturing

Manufacturing

A production line emits events that must never be lost or overwritten, alongside quality and supply records that change. UltraFabric gives the events append-only semantics and the records transactions.

Workload shape

WritesAppend-only events plus record updates
ReadsShift reports, traceability queries
TenancyPlants, lines, suppliers
GuaranteeNo silent replacement
Where the design fits

How the data lands

Design fit, not a customer claim: which parts of UltraFabric carry which parts of this workload.

  • Line events as columnar collections where an existing key is an error, never an overwrite
  • Quality, batch and supplier records as rows under snapshot isolation
  • Per-plant or per-supplier tenants with plant-wide analytics
In SQL

What it looks like

Append-only is a property of the collection, not a convention the application must remember.

CREATE TABLE line_events (id bigint PRIMARY KEY, line text NOT NULL,
  at timestamp, station text, result text) WITH (storage = columnar);

INSERT INTO line_events VALUES (184201, 'L3', '2026-10-23 08:12:04', 'S7', 'pass');
-- a second insert of id 184201 fails: duplicate key (23505)
Status

Built today, coming next

Everything in the first column is in the repository and tested; the second column is the roadmap in order.

Built today

  • SQL INSERT into a columnar collection fails with 23505 on an existing key
  • Compaction moves rows into groups atomically; a snapshot sees each row once
  • Idempotent writes with client keys for retried batches

Next

  • Updates and deletes on columnar collections
  • Automatic background compaction
  • Streaming ingestion

Tell us about yours.

Early access starts with a conversation about the workload you would move first.