Container runtime
Any OCI-compatible runtime — Docker, containerd or CRI-O. The image is published for linux/amd64 and linux/arm64 on every release.
✦ AI · Query explanation
Who stands behind LibreDB Studio commercially — Sekoya, the vendor of record — on which Kubernetes distributions and runtimes, what that support covers, and how to reach us. Separates supported (the commitment) from validated (the published test run).
support.sql
SELECT component, supported, validated FROM supported_platforms;6 rows |3 cols2ms
Commercial support
Who stands behind LibreDB Studio, on which platforms, and how to reach them.
The vendor of record
LibreDB Studio is developed, published and commercially supported by Sekoya Grup Bilisim ve Teknoloji Ltd. Sti. (Sekoya Tech), a company registered in Türkiye. LibreDB is the product brand; Sekoya Tech is the legal entity behind the commitment on this page.
Inkilap Mah. Hasim Iscan Sok. Kent Sitesi F Blok No: 4/33, 34768 Umraniye / Istanbul, Turkiye
Company informationSekoya Tech provides commercial support for LibreDB Studio on every platform and runtime version listed below.Support is available in English and Turkish. LibreDB Studio itself stays MIT-licensed and free — support is a service on top of it, never a paywall in front of it.
Kubernetes and distributions
| Component | Supported | Validated |
|---|---|---|
| Kubernetes | 1.26 or later | v1.31.14, v1.35.5 |
| SUSE K3s | 1.26 or later | v1.31.14+k3s1, v1.35.5+k3s1 |
| SUSE RKE2 | 1.26 or later | — |
| SUSE Rancher Prime and Rancher (community) | 2.9 or later | 2.14.3 (community build) |
| Red Hat OpenShift | 4.15 to 4.22 | — |
| Any CNCF-conformant distribution | 1.26 or later | — |
Supported is what the commitment above covers.Validated is what we have exercised end to end and published a result for; an em dash means the same support terms apply, but no test run is published yet. The chart uses only core Kubernetes APIs and carries no distribution-specific dependencies, so the version floor comes from the chart's kubeVersion constraint rather than from distribution features.
Runtimes
Node.js
Node 20.9 or later; Node 24 LTS is the recommended, fully supported runtime. SQLite database connections need Node 22.13+, and server-side SQLite storage needs Node 24 — the launcher refuses older runtimes with a clear message rather than half-working.
Runtime support tiersWhat support covers
Deployment
Helm chart installation, upgrades and rollback on the platforms above, plus the container and npx paths — including catalog installs (Rancher Apps via a ClusterRepo, OpenShift OperatorHub) and air-gapped installs from your own registry.
Configuration
OIDC single sign-on, role mapping, storage backends, seed connections, ingress and TLS, and the hardened chart defaults (non-root, read-only root filesystem, NetworkPolicy, PDB, HPA).
Defects
Triage and fixes for reproducible defects, shipped in tagged releases. Serious bugs are disclosed in the release notes rather than fixed quietly.
Security
Coordinated disclosure, timely patching of critical vulnerabilities, and advisories published in the repository security tab.
How to reach us
LibreDB Studio is listed in the SUSE Partner Certification & Solutions Catalog, the Red Hat OpenShift community catalog and Artifact Hub.
-- supported is a promise; validated is a receipt. This page keeps them apart.