Skip to main content
An In-VPC (CloudPrem) deployment runs the entire e6data Compute Plane inside your own Azure VNet on AKS. Compute and data stay in your subscription; the e6data Control Plane handles only admin operations, workspace management, access control, and observability. The workspace query endpoint is public by default and protected by JWT auth, or can be made private to your VNet.
Who this is for: your infrastructure / platform team - you need Azure admin access to deploy into your own VNet (creating the VNet, AKS cluster, identities, and storage). Before you start: the Azure CLI, kubectl, and Helm, and familiarity with AKS.
For a fully managed alternative with no infrastructure to run, see Azure Serverless.

​
What you’ll deploy

1

Review the architecture

See Architecture - what runs in your account vs. e6data’s.
2

Check prerequisites

See Prerequisites - required tools and onboarding items.
3

Configure registry, Kubernetes, and networking

Follow Configure registry, Kubernetes, and networking - Azure infrastructure (VNet, AKS, identities, ADLS storage) and the base cluster components (Karpenter, cert-manager, operator, CRDs).
4

Deploy workspace and e6data

Follow Deploy workspace and e6data - the workspace namespace, TLS, identity, and components.
5

Register a catalog

See Register a catalog - connect your data.
6

Create a cluster

See Create a cluster - provision compute.
7

Run your first query

See Run your first query - validate the install.
Ongoing operations are covered in Component versions and operations, Delete workspace, and Troubleshooting.

​
See also

Once your cluster is running, run your first query.
Last modified on September 29, 2026