Connect your databases.
Query with any API or protocol in 5 minutes.

No lock-in — engine or source

Insulate your data consumers from infrastructure churn: your model, semantics, and governance live above the infrastructure, not inside it. Swap the engine — embedded to Trino to your warehouse; new CTO, new strategy, switch it to Databricks — the queries and policies don't change. Re-point a table from Oracle to Postgres, or MongoDB to Snowflake, and consumers never see it move.

That turns data modernization into an incremental effort instead of a big-bang cutover: migrate sources table by table behind a stable governed API, with one uniform governance model applying to legacy and modern sources alike throughout the transition.

Your warehouse should be a replaceable component, not a place you get stranded — when your semantics live above the engine, vendors compete for your workloads instead of holding them hostage.

We don't lock you in either

Provisa is a handful of primitives — domains, tables, relationships, masking, views — compiled deterministically. No proprietary modeling universe to learn, no black box: your model is portable declarative config, and the SQL it compiles is yours to read, export, and keep.

Use it as scaffolding in dev if you want. The semantics you write don't die with the tool — because they were never trapped inside it.

Physical fragmentation, logical coherence

Performance needs fragmentation — the right engine per workload, materialized copies at the right granularity. Consumers need one coherent model. The old cost of fragmenting the physical was fragmenting the logical too: a pile of models with clashing objectives and granularity, physical detail bleeding into logical design.

Provisa splits them. Specialized engines and materialized views underneath, one governed logical model on top — and the physical never bleeds into the contract your consumers see. The knobs that fragment for speed live in the same declarative model that keeps you coherent, so going faster never spawns a second modeling mess.

Domains as products — delegated, not centralized

Give a domain its own owner and scoped rights to build it: register sources, publish tables, wire relationships, ship views — all inside their domain, none of it reaching another. Central policy still governs every query; authorship is federated, enforcement stays absolute. Optional — off by default, on when you need it.

Promote config like code

Analysts and developers work freely in a dev lane — register sources, publish tables, wire relationships. Their changes export as a unified-diff config patch that flows to test, then prod, reviewed in git like any pull request. Because the estate is declarative, promotion is a diff, not a migration.

Where a release also moves data, a materialized view can carry the transform — and land its output into a real source table, not just the internal store. True data migrations may still call for imperative scripts outside Provisa — the model promotes cleanly; the heavy data movement is yours to run.

The economic takeaway — you set the compute bill

Pair semantic governance with intelligent query routing and the value shifts from just managing access to actively optimizing compute economics. Provisa becomes a single point of leverage to optimize execution speed, minimize network egress, and dictate exactly how much you pay vendor compute engines on any given query.