Two independent settings decide what your tenant can do: a feature flag says whether a capability exists for you at all, and your plan says how big an engine you may run. They compose rather than compete — a flag is a switch, a plan is a ceiling. Both are set by a platform administrator, not by anyone in your tenant.
Billing is not enabled yet. Dippr has no checkout, no invoices and no card on file, so nothing in the product charges you. A tenant that signs up for itself starts on the Team plan at no charge while Dippr is in beta; a tenant on any other plan is on it by agreement with Dippr. The prices on the Plan page in your own console, under Settings, are what each plan will cost once billing launches, and you will be told in advance before anything is charged.

Feature flags

If you don’t see one of these surfaces in your console, your tenant likely doesn’t hold the flag for it — ask your platform administrator. A feature flag and the plan are independent: a higher plan raises the engine-size ceiling but never enables a flag on its own. Every new workspace — whether it signed up for itself or a platform admin created it — starts with the standard bundle installed and enabled, regardless of plan: managed_engines, external_connectors, mcp_server, metadata_search, semantic_layer, workspace_databases, pipelines, agents and marketplace. Documents (unstructured_data), plane-local Git (plane_git), secrets and data planes you run yourself (customer_planes) remain opt-in and are not installed at signup. A tenant created before a flag joined the bundle receives it on the next platform upgrade, so the only exception is a flag a platform operator later turned off. Ask your platform operator to change a capability for your tenant. The semantic layer is in that standard bundle, so metric models, business concepts and the review queue are available on every plan, Free included. Nothing about the semantic layer depends on which plan your tenant is on.

Flags that gate acquiring, not holding

The flags below all follow the same shape: they gate acquiring or growing a resource, and never gate seeing or releasing what your tenant already has. If your tenant loses one of these after you’ve already registered engines, databases or connections, nothing already running is taken away or hidden — only getting more of it is blocked. mcp_server does not follow this shape: it is a whole-endpoint switch, covered on its own above, not a per-resource acquire/grow gate. Neither does pipelines: without it, pipelines are not there at all, so listing, running, cancelling and deleting are refused too. Registered pipelines are kept, not deleted, and come back as they were when the flag is turned back on. marketplace is the same shape: without it the Marketplace is not there at all, browsing included, while the drafts it already created stay in your semantic layer.

Engine sizes by plan

Creating an engine without naming a size gives you s if your plan includes it, or the largest size below it that your plan does include. custom is never a default — you have to choose it explicitly, since it means you’re supplying the raw configuration yourself. The engine-size ceiling is the only thing a plan decides. A plan switches no capability on or off, and it caps no count: how many data sources you connect, semantic models you build, apps you publish or people you invite does not depend on which plan you are on. If something you expect is missing, look at the feature flags above, not at the plan.

Where these are set

A platform administrator turns a feature flag on or off per tenant from the platform admin console’s Flags page, and changes a tenant’s plan from its entry on the Tenants page. Neither is something a member of your tenant, including account_admin, can change from inside your own console.

Roles and permissions matrix

The built-in roles Dippr ships with.

Fleet plane acquisition

The per-plane entitlement fleet_plane:<slug> permits acquiring a vendor fleet binding. A platform administrator can explicitly grant and bind from Tenants → Bind to fleet plane. The new tenant option is unchecked by default. Tenant work and secrets run on vendor infrastructure. Revoking the entitlement prevents new acquisition; it does not remove an existing binding, change its default, or revoke its existing access. A binding result reports credential delivery, while Settings → Data planes reports connectivity.