Supporters
Who pays for the parts we do not build
LibreDB Studio is MIT and self-hosted, but the work around it is not free: a build fleet, sixteen database engines to probe against, a public trial anyone can open, signed Windows binaries. Where a company or an open-source programme covers one of those, it is named here.
Current supporters
Supporting the project today
-
Tailscale ↗
The Community on GitHub plan behind the private network maintainers use to reach the database probe hosts, so testing against real engines does not mean exposing database ports to the internet.
Since
-
BrowserStack ↗
Live, Automate and Percy across real browsers and devices. The product is a browser application, so a browser bug is a product bug — and CI can only see desktop Chromium. Safari, older WebKit and mobile layout need hardware.
This project is tested with BrowserStack.
Since
-
Docker ↗
The Docker-Sponsored Open Source programme on the libredb namespace, which removes pull rate limits for everyone pulling the public image. GHCR remains the canonical registry; this is what keeps the Docker Hub mirror usable without an account.
Since
What support means here
The parts that cost money
Each of these is infrastructure the MIT project runs in public. None of them is a feature held back from the repository — the software is complete without any of them; it is the verification and distribution around it that has a bill.
-
Site hosting and CDN
libredb.org and the documentation, plus the release and Helm chart downloads that spike on every version.
-
CI and build capacity
Multi-architecture container builds on every release, and Apple-silicon runners for the desktop build and its notarisation.
-
Security and supply chain
Dependency, container and secret scanning over the public repository and the published package, alongside the checks already in CI.
-
Code signing
An Authenticode certificate for the Windows artifacts. Unsigned binaries teach people to click through the warning, which is the opposite of what a database client should teach.
-
Error tracking and uptime
The two public instances strangers use to evaluate the project — errors, uptime checks and a health dashboard a contributor can read without a paid seat.
-
Browsers and real devices
Automated tests cover desktop Chromium. Safari, WebKit and mobile regressions in a browser-based editor need hardware nobody has on their desk.
-
Developer tool licences
IDE and assistant seats used for maintaining this repository — review, triage and the pull requests that come in from outside.
-
Managed database instances
Every supported engine is probed against a live server, not a mock. Managed instances are how the provider behaviour stays honest against the hosted versions people actually run.
-
Model inference
Credits for the evaluation suite behind the optional AI features, so measuring them does not cost the maintainer per query.
-
Domains and transactional mail
Project hostnames and the mail path that carries security disclosures — the address on the security policy has to work.
The commitment
What a supporter gets, and when
This is the same wording the applications carry, so a reviewer can hold the page against the form.
-
A named entry here, the same day
Name, link and what the support covers — published the day the acceptance lands, not at the next site release.
-
The same entry in the repository
The README carries it too, so the attribution survives someone reading the project on GitHub and never opening this site.
-
The badge the programme requires, kept visible
Where a grant is conditional on specific wording or a mark in a specific place, that condition is stored with the entry and kept, not honoured once and forgotten.
-
Removal on request, without argument
A supporter that ends its support, or simply asks to come off the page, is removed. Attribution is a courtesy that is owed, not a licence to keep using a logo.
The limit
What this page is not
A place on this page cannot be bought. An entry appears here because a programme accepted the project or a company covered a specific cost — never because someone paid for the placement, and never as an advertisement. Donations through GitHub Sponsors are genuinely appreciated and they do not put a name here; they are thanked in the sponsor listing itself. Nothing on this page is an endorsement of LibreDB Studio by the companies named on it, and no supporter has any say in what the project builds.
Who pays for the rest
Supporting the project
LibreDB Studio is developed and published by Sekoya Tech, which funds its maintenance and supports it at no charge. Nothing here is sold: no paid edition, no support contract, no add-ons, and LibreDB Platform — the separate product intended to carry a price one day — is not on sale either. GitHub Sponsors donations supplement the work, and no feature is withheld from the MIT build to create a reason to pay.
If your company runs an open-source programme covering anything in the list above, the fastest path is to say so by email — the applications are being sent either way. Individual support goes through GitHub Sponsors. [email protected] · GitHub Sponsors ↗ · How the project is licensed and run