Sponsorship & support
LensWord is built and maintained in the open. If it's useful to you or your team, sponsoring keeps development moving.
What sponsorship funds
Real, ongoing costs — not a wishlist:
- Maintenance — triaging issues, keeping dependencies current, fixing what breaks.
- Documentation — the guides in this site, kept accurate against the actual code rather than aspirational.
- Cross-platform desktop verification — real macOS, Windows, and Linux hardware/CI time to close the verification gaps recorded in Desktop Application (this documentation pass could only verify Windows; macOS and Linux need separate hardware).
- Release signing and notarization — a macOS Developer ID and Windows code-signing certificate, so installers stop showing Gatekeeper/SmartScreen warnings. Not funded today — every current build is unsigned.
- Hosting — infrastructure for anything beyond what contributors run locally.
- Accessibility work — no accessibility audit has been performed yet; sponsorship could fund one.
What sponsorship does not buy: roadmap priority, security guarantees, or private access. No such policy exists, and nothing here implies one does.
Ways to sponsor
- GitHub Sponsors — individual or organizational.
- Patreon — individual.
- Organizational sponsorship or partnership discussions — email lensword@conectlens.com directly; this isn't a self-service flow.
Getting help — where to go
| If you have... | Go to... |
|---|---|
| A bug or feature request | GitHub Issues — this is where work is actually tracked |
| A security vulnerability | SECURITY.md — not a public issue, and not the sponsorship email above |
| A sponsorship or partnership question | lensword@conectlens.com |
| A general product question | lensword@conectlens.com, or open a GitHub Issue if it's something others would benefit from seeing answered |
| Code or documentation to contribute | Contributing |
No response-time guarantee exists for any of these channels.
More context
- Contributing — development setup and the pull request process.
- Code of Conduct
- Changelog — what's shipped so far.
- Roadmap — what's planned; sponsorship doesn't reorder it.
- Trust & verification — what's actually been tested, stated plainly.