2026 roadmap

[KevinX1992]

I see that there’s no content for 2026 in the roadmap. Has the 2026 roadmap been confirmed, and what are the key priorities.

[roryqi]

Maybe you can refer to https://gravitino.apache.org/blog/2025-summary/

[markhoerth]

Hi @KevinX1992, thanks for your note, and thanks @roryqi for the 2025 recap link (good context for where we're coming from).

The 2026 roadmap is actively being shaped, so your timing is good. Rather than me guessing at what would be most useful to share, I'd love to hear from you first:

• What's your use case with Gravitino, and what does your stack look like around it?
• What's the biggest gap or pain point you're hitting today?
• Are there particular areas you're most interested in — e.g. catalog/connector coverage, security and governance, IRC, operations, UI, AI/ML asset management, or something else?
• Is there a specific timeframe you're planning against?

The more concrete you can be, the more useful the conversation will be, and this kind of input is exactly what helps prioritization. Happy to take it deeper here or in a GitHub issue if that's easier.

[Etherdaemon]

Hi @markhoerth,

I'd like to know as well on what's coming and what priorities there are for Gravitino in the immediate future.

For the company I work for, we're currently a heavy Databricks customer but we're evaluating Gravitino + other components for a use case which requires us to span across multicloud (AWS and GCP), multi-region and a multi-tenant-like setup. We're looking at having a single Gravitino instance that has S3 and GCS catalogs backed by Postgresql and Iceberg Rest Catalog with credential vending. Our query engines are likely Starrocks, Spark and Ray with some possible front end solutions such as Jupyterhub and Superset.

Our biggest items that we care about for this use case is governance, so items like ABAC enforcement, catalog level lineage, table/path level scoped credential vending, TTL for table and row level expiration, tagging for classifications with cascade as well as policy enforcement. We plan on integrating Apache Ranger to help support some of these items but would love to be able to drop this plugin requirement if it can be supported within Gravitino natively.

We care about auditing and monitoring as well although I haven't had a chance to delve into Gravitino's capabilities here just yet to see what the gaps are.

Are there any plans to support some kind of secrets management as well or is the best course of action here to use the cloud provider secrets management solutions instead?