Vendor support
Who stands behind LibreDB Studio
The software is MIT and free, and so is the support behind it: there is no paid tier, no support contract to buy and no capability withheld from anyone who does not pay. What this page states is who is answerable for the software, on which platforms and versions, and how to reach them.
The vendor of record
LibreDB Studio is developed, published and 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
Sekoya Tech supports LibreDB Studio on every platform and runtime version listed below, at no charge. Support is available in English and Turkish. Nothing on this page is sold; it is the commitment the publisher stands behind, published so a certification reviewer can check it.
Kubernetes and distributions
Supported versions
| 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 has been exercised
end to end with a published result; 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 its kubeVersion constraint rather than from any distribution's features.
Deployment and validation record ↗
Runtimes
What it runs on
- Container runtime
- Any OCI-compatible runtime — Docker, containerd or CRI-O. The image is published for linux/amd64 and linux/arm64 on every release, so an Apple silicon laptop and an Ampere node run the same tag as an x86 server.
- Node.js
- Node 24 LTS or later, on Linux, macOS (x64 and arm64) or Windows (x64). Node 24 is the reference runtime — it is what the release payload is built on — and Node 25 and 26 run that same payload, native module included. Below 24 npm does not error; it silently resolves an older release instead, which is why the floor is stated rather than assumed. Runtime support tiers ↗
Scope
What 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, PodDisruptionBudget and 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.
Verifiable listings
Where this is on the record
Every listing below is live and can be opened. A submission that has been opened but not merged is not a listing, and does not appear here until it is one.
Contact
How to reach us
- Support enquiries
- [email protected]
- Vulnerabilities
- SECURITY.md ↗
- Bugs & questions
- GitHub issues ↗
A vulnerability goes to the address in the security policy, never into a public issue — the policy exists so a fix can ship before the details do. How the security model works →