Platform components
What makes up the e6data Control Plane and Compute Plane, and where your data sits relative to each.
e6data is organized into two planes plus your data. The Control Plane is shared across your organization; each workspace has its own Compute Plane; your data always stays in your cloud account.
Control Plane
The shared e6data Console, hosted by e6data. It manages your organization and never processes queries or touches your data.
Organization and account
Tenancy, membership, and billing
Workspace management
Create, open, disable, and delete workspaces
Global access control
Users, groups, roles, and SSO
Releases and monitoring
Version management and platform telemetry
Compute Plane
The workspace-scoped environment you enter by clicking Open on a workspace in the Control Plane. This is where data work happens.
Catalogs
Connections to your metastores (Catalogs)
Clusters
The compute that runs queries (Clusters)
SQL Editor
Write and run queries in the browser (Query editor)
Run History
A searchable log of every query (Query history)
Settings
Access control, version upgrades, observability, and connectivity
Whether the Compute Plane runs in e6data's cloud or in your own Kubernetes cluster depends on the deployment model.
Your data
Your data lives in your own object storage (S3, ADLS Gen2). e6data reads it in place through an identity you grant, and it is never moved or copied. The catalog supplies the metadata that tells e6data how to interpret it.
See also
Last updated
Was this helpful?