Skip to main content

Services

What a stardelt install contains. For how the services connect, see How it works. Each service has its own page with settings and operating notes.

Always installed​

These form the core: make install-core, or the umbrella chart's default values.

ServiceWhat it doesLicense
stardelt NovaThe web interface and the API: catalog, SQL editor, loads, connections, pipelines, query log, lineage, healthApache 2.0
Apache TrinoThe SQL engine for interactive queries, the SQL editor and dashboardsApache 2.0
LakekeeperThe Iceberg REST catalog: which tables exist and which files belong to themApache 2.0
SeaweedFSS3-compatible object storage, or bring your own S3-compatible storeApache 2.0
CloudNativePGRuns the PostgreSQL databases of the platform's servicesApache 2.0

Apache Iceberg (Apache 2.0) is the open table format every engine reads and writes. It is not a service you install: it lives inside the engines and the catalog.

Optional​

Each of these is built and off by default in the core. make platform installs them too, except where the table says otherwise.

ServiceWhat it doesTurn it onLicense
KeycloakSign-in. Optional: the OIDC provider stardelt can deployIDENTITY=1, or identity.mode in the chartApache 2.0
OpenFGAStores who may do what on which tablewith make platformApache 2.0
Open Policy AgentAnswers Trino's permission questions, next to Lakekeeperwith make platformApache 2.0
Apache AirflowRuns scheduled pipelinesmake installApache 2.0
Apache SupersetDashboards over Trinomake installApache 2.0
JupyterHubNotebooks for each personmake install-notebooksBSD-3-Clause
Apache Spark (Spark Connect)Distributed compute for jobs that outgrow Trinomake install-sparkApache 2.0
OpenBaoStores connection secrets. Not installed by make platformmake openbaoMPL 2.0, the one license exception
cert-managerIssues TLS certificates. A cluster prerequisite for sign-in, not installed by stardeltPrerequisitesApache 2.0

stardelt's own control plane​

The stardelt Operator (Apache 2.0) turns small resources, such as PlatformInstance, Lakehouse, Catalog and Pipeline, into running services. It installs separately with make install-operator. Resources are described in the resource reference.

How a service gets in​

A service joins the platform only if it meets all of these:

  1. License: accepted by the license policy.
  2. Maturity: real users, active commits, recent releases.
  3. Kubernetes: deploys cleanly, ideally with a maintained operator or chart.
  4. Sovereignty: no required outbound calls at runtime.
  5. Open contract: it sits behind a published interface (SQL, Iceberg REST, S3, OIDC), so it can be replaced.

What may come later is on the roadmap.