Run LakeSentry entirely inside your own infrastructure.
The Private Cloud deployment gives your team full control over where data lives, how it is stored, and who can access it. Deploy via Docker or Kubernetes in your own VPC — nothing leaves your environment.
Contact us for a private cloud license and deployment guide.
Prefer a Databricks-native install? Try the Databricks App.
Maximum control. Zero external dependencies.
For organizations where data residency and infrastructure isolation are non-negotiable.
Complete data isolation
The LakeSentry application, cost ledger, and insights engine all run inside your VPC. No data ever leaves your infrastructure boundary.
Bring your own database
LakeSentry runs on PostgreSQL. Point it at your existing managed instance — RDS, Cloud SQL, Azure Database, or on-prem. You own the data entirely.
Network-level controls
Deploy behind your existing firewall and VPN. Apply your own security groups, IAM boundaries, and audit tooling without any changes to LakeSentry.
Compliance-ready
Meets data residency requirements for regulated industries. All processing happens within your environment under your policies and governance controls.
Four components.
Your infrastructure.
The same LakeSentry product, packaged for self-hosting. All components run inside your VPC, governed by your existing policies.
-
Application container
The full LakeSentry web app and API — dashboards, cost explorer, insights, approvals, and audit — served from a single Docker image in your environment.
-
Cost ledger
Normalized job, pipeline, SQL, and compute usage materialized into PostgreSQL tables you own. Schema migrations are included in each release.
-
Insights engine
Anomaly detection, waste identification, and significant-work ranking computed on a configurable schedule within your infrastructure.
-
MCP Server
Expose LakeSentry as a tool surface to your AI agents or Databricks Genie, scoped to your Unity Catalog permissions and served from your network.
Up in four steps.
Provision a database, create a service principal, deploy the container, and start seeing data. Contact us and we’ll guide you through it.
- 1
Provision a PostgreSQL database
LakeSentry stores its cost ledger and application state in PostgreSQL 14+. Any managed or self-hosted PostgreSQL-compatible instance works — RDS, Cloud SQL, Azure Database, or Supabase.
- 2
Create a read-only service principal in Databricks
LakeSentry needs SELECT access to Unity Catalog system tables to ingest cost and usage data. Create a service principal and grant it the minimum required permissions.
- 3
Deploy with Docker or Kubernetes
Pull the LakeSentry container image using your private cloud license key. Configure the environment variables pointing at your database and Databricks workspace, then start the container.
- 4
Open LakeSentry and invite your team
Navigate to your deployment URL, complete the initial setup wizard, and invite your team members. Cost data begins ingesting immediately.
Private Cloud FAQ
Common questions before deploying LakeSentry on your own infrastructure.
What infrastructure do I need?
A PostgreSQL 14+ database and a container runtime (Docker or Kubernetes). LakeSentry is a single container — no separate message queues or additional services required.
Does any data leave my environment?
No. With the Private Cloud deployment, LakeSentry runs entirely inside your VPC. The only outbound call is a periodic license check to verify your subscription status.
How do I get a private cloud license?
Contact us via the form below or at support@lakesentry.io. We will provide a license key, a deployment guide tailored to your environment, and onboarding support.
How are upgrades handled?
We publish new container images with semantic version tags. Pull the new image, run the included migration script against your database, and restart the container. Downtime is typically under a minute.
Is Kubernetes required?
No. A single Docker container is sufficient for most teams. We also provide a Helm chart for teams that prefer Kubernetes-native deployment with horizontal scaling and rolling updates.
How is this different from the Databricks App?
The Databricks App runs inside your Databricks workspace using Databricks Apps runtime and Lakebase. Private Cloud runs on your own servers or cloud VPC with your own PostgreSQL. Choose Private Cloud when your team already manages container infrastructure or when you need isolation outside the Databricks boundary.
Deploy LakeSentry in your own environment.
Get a private cloud license and a deployment guide tailored to your infrastructure. We’ll help you get up and running.