Everything you do in the console — signing in, registering an integration, browsing a catalog — goes through Dippr’s control plane. Your actual data, and the compute that touches it, live somewhere else: a data plane. A data plane is a cluster that runs your connectors, your query engines, your MCP endpoint and your data apps. When you register an integration, its credentials are sealed to a specific data plane and decrypted only there. When you provision a query engine, it’s the data plane that stands the cluster up. The control plane never stores a readable integration credential (it receives one once, over TLS, and seals it to the plane) and never sees a query result pass through it. It coordinates; the data plane does the work. Metadata and query text do reach it; see What leaves your data plane.
A shared plane on Dippr cloud, or your own plane inside your cloud account; both connect outbound to the control plane

Shared plane, or your own

Every tenant starts with a shared plane — infrastructure Dippr operates, alongside other tenants’ work, in Dippr’s own cloud account. For most tenants this is all they ever need. A tenant created through self-serve sign-up sees this reflected on Settings → Data planes with a banner and a vendor chip — see Register or join a plane. If your data has to stay inside your own cloud account or network, you can register your own plane instead: a cluster you run, connected to Dippr’s control plane over an outbound-only link. Your plane dials out to Dippr; nothing in Dippr’s control plane dials in. (Your own users and AI clients still connect to the plane’s endpoints, see which AI clients can reach a private MCP endpoint.) Two things follow from that:
  • Dippr’s control plane never needs network access into your infrastructure.
  • Your connectors, engines and apps run entirely inside your own account, under your own network policy.
This is sometimes called BYOC (bring your own cloud). Registering one is covered in Register or join a plane.

Several planes in one tenant

A tenant can have more than one data plane at once: the shared plane plus a plane you operate yourself, or several of your own planes in different regions or clouds. Nothing forces you to consolidate. Each integration, query engine, app installation and workspace database belongs to exactly one plane. You choose the plane when you register or create the thing — an integration’s register form, an engine’s register form, and so on all offer a plane picker. Your tenant has one default plane (the first one you registered), which is what a plane-less create falls back to, and what a headless tool like dip app push targets when you haven’t named one explicitly.

Addresses

Every hostname on a plane — an engine’s endpoint, your MCP server, your app installations, your image registry — is a label under that plane’s own domain, never the control plane’s. Two planes never share a domain, so an engine’s URL alone tells you which plane it runs on. See Addresses and hostnames for the full hostname list.

What you can’t do across planes

An integration’s credentials are sealed to the plane it’s registered on, so a query engine can only mount catalogs from integrations on its own plane — pointing an engine at another plane’s integration isn’t an option the console offers. Likewise, a data app pushed to one plane’s registry can only be installed on that same plane.