Datastrato Enterprise

Datastrato Enterprise is a commercial distribution of Apache Gravitino. It runs the same engine, speaks the same API, and uses the same concepts, with the operational capabilities an organization needs to put a metadata lake into production.

If you have used Apache Gravitino, everything you know still applies. Metalakes, catalogs, schemas, and tables mean what they always meant. Configuration keys, REST endpoints, client libraries, and connector names are unchanged. The documentation says "Gravitino" when it means the engine and "Datastrato Enterprise" when it means the distribution and what it adds.

What Enterprise Adds

Identity and access. SCIM provisioning from your identity provider, so users and groups arrive from the directory you already run rather than being maintained separately, alongside local accounts for when the identity provider is unavailable. Role-based access control enforced across every federated catalog, including requests that arrive through the Iceberg REST catalog.

Operations. A supported Helm chart, health and readiness endpoints wired for orchestration, and metrics for every service the server runs.

Governance. Tags, policies, and ownership across every connected source, with coverage reported per catalog and per asset type, an audit log of metadata operations, and lineage collected from Spark through OpenLineage.

The administration UI, for catalog connection, access review, and monitoring.

Support, with a defined response commitment and a maintained release line.

Getting Started

Deployment is a Helm chart pulled from a registry, installed into a Kubernetes cluster, and activated with a license key.

Start with Requirements to confirm your cluster is suitable, then Getting started to install and reach a working system.

To try it on a laptop rather than a cluster, Local evaluation runs the same chart against a local Kubernetes.

Where to Go Next

Connect sources covers attaching your first catalog, whether that is a lakehouse, a metastore, a relational database, or object storage.

Explore metadata covers the object model: how catalogs, schemas, tables, filesets, and models are organized within a metalake. Architecture and Concepts describes how the pieces fit together.

Authorize access covers roles, users, and groups, and granting access to what you have connected.

Engines and agents covers querying through Trino, Spark, Flink, and anything that speaks the Iceberg REST protocol.

Relationship to Apache Gravitino

Apache Gravitino is a top-level project of the Apache Software Foundation. Datastrato employs many of its contributors and maintains this distribution on top of it.

The engine in Datastrato Enterprise is Apache Gravitino. Your metadata is stored in open formats, your catalogs are addressable through the standard API, and nothing in the data path is proprietary. Migrating between the two directions does not require rewriting your integrations.

The upstream project documentation is at gravitino.apache.org. Where this documentation and the upstream documentation differ, this one describes what Enterprise does.