Provisa / Works with / Provisa and Hasura
Provisa builds on the Hasura idea.
Hasura DDN gives you instant, per-role GraphQL APIs over your own databases, metadata-driven, with a connector-per-source model for federation. Provisa shares that core idea and extends it with more languages, more protocols, federation defined in the model and run on the engine you choose, and governance that holds identically on every entry point.
What Hasura keeps doing
- Metadata-driven per-role GraphQL schemas, with cursor pagination, aggregates and subscriptions
- A connector per source, with lambda functions for custom logic
- Your application's API, with its permissions and connectors in place
What Provisa adds
- pgwire, Bolt, Arrow Flight, gRPC, REST, WebSocket, Airport and MCP alongside GraphQL, all on the same model and policy
- Cypher as a first-class language, over relationships registered and governed in the model
- Cross-source joins in the engine you choose, with statistics and spill-to-disk for large joins
- An MCP server where the OAuth token maps to a role, under the same six access-control layers as a person
Use them together
If you already run Hasura DDN for your application's GraphQL API, Provisa can provide the governed semantic layer underneath it, or alongside it for other languages and workloads. Your Hasura permissions and connectors stay in place.
They complement each other most directly when Hasura handles the immediate app API with its DDN supergraph and Provisa handles the SQL analytics layer, the graph traversals and the MCP connection that agents use. Both draw from the same underlying databases.
One command
# Read a Hasura v2 metadata directory, write a Provisa config
python -m provisa.hasura_v2 ./hasura/metadata -o provisa.yaml
# Validate without writing, map schemas onto domains, override connections
python -m provisa.hasura_v2 ./hasura/metadata --dry-run
python -m provisa.hasura_v2 ./hasura/metadata --domain-map public=sales billing=finance
Sources, tables, row permissions, relationships, remote schemas, actions and event triggers all convert. Roles and rate limits come across as Provisa roles. Anything that doesn't map cleanly becomes a warning, so you get a list to work through and no silent gaps.
What you keep coming from Hasura v2
A per-role API over your database, generated from metadata, with permissions enforced at query time. Per-role schemas, field-level visibility, cursor pagination, aggregates and Apollo Automatic Persisted Queries all carry across. You have no new modeling universe to learn, and you don't pay for the move with a rewrite.
If you only need Hasura DDN
Your application speaks GraphQL. Your data lives in relational databases you own. You want a metadata-driven connector-per-source model with lambda functions for custom logic, and PromptQL handles the AI access your team needs. Hasura DDN covers that well on its own.