Built for teams that need the data to stay inside their cluster.
Managed data warehouses keep the control plane at the vendor and charge per credit. stardelt runs the whole stack inside your Kubernetes cluster — same engines, same SQL, same ML — operated by you.
Hyperscaler, sovereign cloud, on-prem, edge, air-gapped. The control plane is operators in your cluster — there is no SaaS side.
No telemetry, no license check, no usage report. Each release ships with a documented network-egress matrix listing every call its components make.
Apache 2.0 / MIT / BSD across the stack. Services on BSL, SSPL, ELv2 or AGPL are excluded by policy.
A small set of top-level CRDs (Lakehouse, Pipeline, StreamApp) reconcile into the per-service operators, instead of asking platform teams to assemble them by hand.
SSO, catalog browser, lineage view, cost attribution, audit search, and deep-links into the underlying tools. One place to start for engineers, one place to look for auditors.
Tables are Iceberg + Parquet on object storage. Uninstalling stardelt leaves your data readable by any Iceberg-compatible engine — no proprietary metadata to peel off.
An opinionated collection of services on a shared foundation.
Modern 2026 service picks on a shared Iceberg + Lakekeeper foundation. Composed by the stardelt Operator and surfaced through stardelt Nova.
Lakehouse SQL
Interactive SQL over Iceberg tables on object storage.
Compute & orchestration
Spark Connect for distributed jobs, Airflow for scheduling.
Streaming
Kafka as the event backbone; Flink (opt-in) for stream processing.
Notebooks & BI
JupyterHub for analysis, Superset for dashboards — both wired into Trino and Spark.
For environments where data has to stay in your perimeter.
Every release publishes a network-egress matrix. Every outbound call is listed; nothing undocumented at runtime.
Helm/OLM bundles ship every image. Harbor (or any OCI registry) as the in-cluster mirror; no DNS to external hosts required at install or upgrade.
CI runs installs on European sovereign-cloud Kubernetes (STACKIT, OVHcloud, IONOS, Hetzner, Open Telekom Cloud, Scaleway) alongside the hyperscalers.
Default install pulls only from the Apache Software Foundation, CNCF, Linux Foundation and vendor-neutral projects. Useful when GDPR Article 28 or the US CLOUD Act are in scope.
The full design lives in the docs.
Architecture, component selection, licensing analysis, diagrams — load-bearing for everything that comes later. The codebase is pre-alpha; the docs are where the design is settled.
Architecture
How the core stack and opt-in services compose on Kubernetes, and how requests flow between them.
Read the architecture →Services
Per-service descriptions, licenses, and upstream links for the core stack and the opt-in services.
Browse services →Roadmap
Phases 0 through 6, what ships when, and an explicit list of what is out of scope for v1.
See the roadmap →