Use cases

Built for the Most Demanding Industries

The industries below share one need: many parties on one platform, each seeing only its own data, with analytics over all of it. That is the problem UltraFabric's verifier is built to solve. Nothing here is a customer claim; it is where the design fits.

Discuss your workload Platform overview

Isolation per query

Every plan is checked on the data node before it runs.

Events and records

Columnar for the firehose, rows for the ledger, one schema model.

PostgreSQL in front

psql connects today; drivers follow with the extended protocol.

Industries

Where the design fits

Airports & Aviation

Operations data, sensor streams, video analytics and passenger flows in one tenant-safe store.

Operations and asset records as row collections
Sensor and flow telemetry as columnar collections
Per-airline or per-agency tenants on one cluster

Today: Row and columnar storage with verified isolation; vector and streaming engines planned.

Read the Airports & Aviation page

Smart Cities

Traffic, public safety and utility telemetry where every department sees only its own rows.

Department-scoped tenants with isolation checked per query
Traffic and utility counters as append-only events
Field masking by clearance for citizen data

Today: Clearance-based field masking is enforced in the verifier; row-level policies are next.

Read the Smart Cities page

Power & Utilities

Grid telemetry and asset records; columnar storage for the time series, row storage for the records.

Measurement streams as columnar row groups with zone maps
Asset and work-order records as rows
Analytics with answers that equal DuckDB's

Today: TPC-H style analytics run; a time-series engine measured on TSBS is planned.

Read the Power & Utilities page

Public Sector

Multi-department deployments on one cluster with isolation checked on every query, not configured per app.

Many departments, one platform, isolation that cannot be optimised away
Audit of every verifier decision
Self-hosted on your own hardware

Today: Single-node self-hosted; replication and the control plane are the next phase.

Read the Public Sector page

Manufacturing

Line telemetry, quality records and supply data; append-only columnar collections for events.

Line and quality events in append-only collections
Duplicate keys rejected at insert, never silently replaced
Snapshot reads that see each row exactly once

Today: Columnar compaction runs after inserts; background compaction is planned.

Read the Manufacturing page

Healthcare

Patient and operational data with field-level masking by clearance, enforced on the data node.

Patient fields above a user's clearance masked on the node
Operational analytics over the same tables
Tokens verified at the gateway and again at the node

Today: Field masking and tenant isolation are built; row policies and index probes are open items.

Read the Healthcare page

Transportation

Tolling, fleet and mobility analytics with tenant boundaries that are a key range, not a filter.

Tolling and trip events as columnar collections
Fleet records as rows with idempotent writes
Tenants for operators and authorities on one cluster

Today: Row and columnar engines built; the managed service follows replication.

Read the Transportation page

Research & AI

Verified plans today; vector and search engines on the roadmap behind the same verifier.

A specified plan language with canonical encoding and fingerprints
A verifier whose core is mechanised in Lean 4
Vector and search operators specified behind the same rules

Today: Verified plans today; vector, search and graph engines are specified, not built.

Read the Research & AI page

Tell us which of these is yours.

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

Request early access