Provisa / Works with / Provisa and Starburst
Keep Starburst. Put a governed model on top.
Starburst runs SQL analytics at scale in a managed Trino lakehouse, with Gravity for tags and ABAC and Galaxy for data products. Register it as the query engine in Provisa and it keeps doing all of that. Provisa adds a governed model over the same data, and more ways to reach it.
What Starburst keeps doing
- SQL federation and analytics at cluster scale
- Gravity for tags and ABAC
- Galaxy data products, and agent access over SQL
What Provisa adds
- GraphQL, Cypher and SPARQL over the same data
- Governed transactional writes routed direct to the source driver, in under 100 ms
- Consistent policy on every protocol, MCP agents included
- Publishing to external catalogs and importing from your semantic layer
Use them together
Register Starburst as the query engine in Provisa. Starburst keeps doing what it does well: SQL federation at scale, Gravity ABAC, and Galaxy data products. Provisa adds GraphQL, Cypher and SPARQL over the same data, governed transactional writes routed past the engine, and consistent policy on every protocol, MCP agents included. Starburst's data products and Gravity stay exactly where they are.
Your semantics and policy stop living inside the engine, so you can replace it later if you ever need to.
If you only need Starburst
Your consumers are SQL and BI tools. You want one vendor's managed Trino platform with governance (Gravity), curated data products, and agent access over SQL. You are committed to Trino as the engine. Starburst covers that well on its own.