UNITRONIX
87e6cd7320
Also add always-apply Cursor rule to update SPONSORS.md and push to main promptly when a new supporter arrives.
8.0 KiB
🏆 BetterDesk Sponsors & Honorary Supporters
BetterDesk would not be where it is today without the support of organizations and individuals who believe in open, secure, and self-hostable remote-management software. This page acknowledges them with our deepest gratitude.
🥇 Honorary Supporters
INSOLVE
INSOLVE is recognized as an Honorary Supporter of the BetterDesk project. Their support has directly contributed to security audits, hardening work, and the continued development of the BetterDesk Go server, web console, and operator/agent clients.
- Website: insolve.pl
- Role: Honorary Supporter
- Contribution areas: Security review, production audits, infrastructure testing, real-world deployment feedback.
Thank you, INSOLVE, for backing free and open remote-desktop software. 🙏
☕ Individual Backers
These supporters keep the project going through one-time and recurring donations. Thank you — every coffee counts. ☕
Marco Jakobs (@jacotec)
Marco Jakobs backed BetterDesk development with a generous donation via Buy Me a Coffee. We are grateful for the support and for believing in open, self-hostable remote-management software.
Thank you, Marco! 🙏
MyNameisStitch (@MyNameisStitch)
MyNameisStitch backed BetterDesk with a generous donation via Buy Me a Coffee, and contributed a detailed Web Remote / reverse-proxy report that helped clarify documentation for other operators (#329).
Thank you, MyNameisStitch! 🙏
Redspin (@playerumpknow)
Redspin backed BetterDesk with a generous donation via Buy Me a Coffee. We are grateful for the support and for believing in open, self-hostable remote-management software.
Thank you, Redspin! 🙏
💖 How to Sponsor
BetterDesk has been growing rapidly — from a passion project driven by vibe coding into a tool that individuals and commercial companies rely on every day. To ensure that BetterDesk remains stable, secure, and continuously updated with new features, we have officially opened sponsorship and donation options.
Choose whichever platform suits you best:
- Monthly or Tiered Sponsorship: Become a GitHub Sponsor
- One-time Donations: Buy Me a Coffee
💡 Where does the money go?
Your support directly fuels the development of the project. The funds are used for:
- AI Development Tools — Covering the subscription costs of tools like GitHub Copilot, which allows us to prototype and ship new features at lightning speed.
- Infrastructure & Testing — Maintaining the necessary environments to keep the code clean and stable.
- Fueling the Creator — Simply buying the maintainer a coffee (or a meal!) to compensate for the private free time invested into coding this project late at night and during weekends.
🎁 Supporter Perks & Tiers
Perks match the tiers configured on
GitHub Sponsors and
Buy Me a Coffee (see also
.github/funding.yml).
☕ Buy Me a Coffee — one-time
| Platform | buymeacoffee.com/unitronix |
| License | AGPL-3.0 (same as everyone) |
| Commercial Grant | ❌ Not included |
Perks: thank you, optional mention in this file (with permission).
GitHub Sponsors — monthly tiers
| Tier | Price | Perks | Commercial Grant |
|---|---|---|---|
| ☕ Buy me a Coffee | $5 / month | Sponsor badge on GitHub, gratitude | ❌ |
| 🍕 Pizza Fuel | $15 / month | Badge + your name in the repo thanks section | ❌ |
| 🏢 Bronze Sponsor (Backer) | $50 / month | Company link or small logo in README; priority triage (best-effort, no SLA) | ✅ |
| 🚀 Silver Sponsor (Priority Support) | $100 / month | Medium logo + backlink in README/docs; priority triage; email for bugs/config; roadmap input; sponsor-funded upstream features stay open under AGPL-3.0 | ✅ |
| 👑 Gold Sponsor (Core Partner) | $200 / month | Large prominent logo in README/docs; all Silver perks | ✅ |
Individual tiers ($5 / $15) fund tools and maintainer time. Bronze and above are corporate tiers — they include the self-service Commercial Grant (private deployment patches without copyleft, while sponsoring).
Tip
If a tier description on GitHub Sponsors still mentions Apache 2.0, the repository policy is AGPL-3.0 — see LICENSE.
🥇 Honorary Supporters
Significant non-monetary contribution (audits, infrastructure, mentorship).
- Logo + dedicated section in
SPONSORS.mdand README badge - Commercial Grant included (docs/COMMERCIAL-GRANT.md)
Note
Governance: To maintain maximum security and architectural consistency, all development remains strictly in the maintainer's hands (no external PRs accepted for now). Sponsorship does not grant ownership or veto power over the project's roadmap, ensuring BetterDesk remains independent and secure.
Sponsorship Terms & Boundaries
By becoming a Sponsor you acknowledge and accept the following terms. These rules exist to ensure high code quality, full transparency, and to protect the long-term health of the project and its creator.
No Hiding or Commercializing Upstream Changes
No modification, feature, or fix merged into the public BetterDesk repository during a sponsorship engagement may be hidden from the community, locked away from upstream, or sold as a paid add-on unavailable to others. Everything built with sponsorship support and merged upstream is available to everyone under the AGPL-3.0 license.
This rule applies to upstream project code. It does not require sponsors to publish private patches that exist only in their own deployment — that is what the optional Commercial Grant covers for eligible tiers.
Best-Effort Model (No Guaranteed SLA)
This is a solo, spare-time project. There is no guaranteed response time, no license audits, and no admin overhead for sponsor grants — GitHub Sponsors billing is the only check. Development, fixes, and replies happen when the maintainer has time.
Communication
All change requests and bug reports should go through GitHub Issues to maintain project transparency. If sensitive information needs to be shared (e.g. proprietary configuration details, company logs), email communication is also acceptable.
Full Code Control (No External PRs)
To maximize security (protection against unauthorized code injection) and architectural consistency, all development is performed exclusively by the lead maintainer. External code contributions (Pull Requests) from third-party developers are not accepted at this time, eliminating the risk of unwanted software injection.
Creator Independence (BDFL)
Sponsorship does not entitle a sponsor to exert pressure, dictate architectural changes, or push features that conflict with the project's core vision. The final decision on the shape of the code and the direction of development always belongs to the creator.
Other ways to contribute
- Code contributions: see CONTRIBUTING.md
- Security disclosures: see docs/security/
- Commercial Grant / corporate partnership: see docs/COMMERCIAL-GRANT.md or open an issue.
- Honorary supporter status: open an issue or contact the maintainers via the repository.
Last updated: 2026-07-31