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

Use case · Healthcare

Healthcare

Clinical platforms serve clinicians, administrators, researchers and partners with very different rights over the same records. UltraFabric masks fields by clearance inside the plan, so no application path can forget to.

Workload shape

WritesRecords, device telemetry
ReadsPoint lookups, cohort analytics
TenancyFacilities, partners, research
SensitivityHighest; masking by clearance
Where the design fits

How the data lands

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

  • Patient records as rows with field classification; fields above clearance are masked in the plan
  • Operational and device telemetry as columnar collections
  • Per-facility or per-partner tenants
In SQL

What it looks like

A requester below the clearance of the notes field receives NULL for it in every plan, including aggregates.

CREATE TABLE encounters (id bigint PRIMARY KEY, mrn text NOT NULL,
  seen timestamp, unit text, diagnosis text, notes text);

SELECT unit, count(*) FROM encounters
 WHERE seen >= '2026-10-01' GROUP BY unit;
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

  • FIELD_MASK is a mandatory plan operator checked by the verifier
  • Identity, tenant and clearance come only from the verified token
  • Error messages carry no hidden-row identifiers or byte counts

Next

  • Row-level policies compiled on the node
  • Index probes with per-label partitions for confidential classes
  • Audit anchoring

Tell us about yours.

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