Skip to main content
Elementary Runtime is in private beta. Reach out to the team to learn more.
Elementary Runtime lets Elementary Cloud run supported data-quality queries inside your environment. You keep the warehouse credentials that can read your business data, while Elementary Cloud continues to manage tests, schedules, results, and incidents.

​
How it works

Elementary Runtime is a small service that runs in your network. It uses an outbound HTTPS connection to request work from Elementary Cloud, validates each query locally, and runs approved queries with customer-managed warehouse credentials.
Elementary Runtime architecture: the runtime pulls pre-approved tasks from Elementary Cloud over outbound HTTPS, runs them locally against data systems in the customer environment, and returns bounded results to Cloud
Elementary Cloud remains the control plane. It decides what should run, prepares the SQL, schedules tests, interprets results, and manages incidents. Elementary Runtime is the data plane for supported operations. It checks and executes the SQL, then returns only the result needed by the Cloud workflow.

​
Why use Elementary Runtime

Keep data access in your environment

Credentials that can read your business tables stay with the runtime in your network.

Apply guardrails locally

The runtime checks SQL before execution and enforces local limits for time, concurrency, and result size.

Control what leaves your network

Queries return bounded results. Row samples can be limited or disabled for sensitive workloads.

Keep the managed Cloud experience

Elementary Cloud continues to handle scheduling, test results, health visibility, incidents, and alerts.

​
Set up Elementary Runtime

Configuration

Configuration file reference, local limits, secrets, and least-privilege warehouse roles.

Deployment

Run the runtime as a Docker service or on Kubernetes with the Helm chart.