Feature matrix

This feature matrix tracks what Ursa supports today across formats, clouds and catalogs. It mirrors the matrix maintained in the ursa-storage repo at docs/feature-matrix.md, and reflects Ursa 5.0.0-M1 — as a milestone release, the rows marked not supported or in progress are the ones most likely to change before 5.0. ✔ marks supported, ✖ marks not supported, and "in progress" is called out explicitly where the source does so.

Data formats

Entry format is what's read off the wire; WAL object and compacted object formats are how Ursa stores that data internally, before and after compaction.

Entry format

WAL object format

Compacted object format

Storage backends

WAL storage splits into a latency-optimized tier, still maturing, and a cost-optimized tier already supported across all three major clouds.

WAL storage

Latency-optimized backends:

Cost-optimized backends:

Lakehouse storage

Schema

Ursa supports using either Pulsar Schema or Kafka Schema.

Kafka Schema

Kafka schema integration works with the StreamNative Kafka Schema Registry and the Confluent Schema Registry.

Lakehouse tables

Table format and catalog support determine which query engines can read Ursa's compacted output without a conversion step.

Table format

Catalog