New features
Persistence improvements, authentication layers, deployment packaging, and sponsor-driven feature requests.
Open-source funding
Sponsorship funds the engineering work around the EUPL-licensed open-source edition: features, documentation, security reviews, release maintenance, and long-term project continuity. From the Backer tier upward, sponsors can submit prioritized feature requests.
Funding areas
Support is directed at practical project work that makes the software easier to run, inspect, and trust.
Persistence improvements, authentication layers, deployment packaging, and sponsor-driven feature requests.
More guides, API examples, diagrams, and tutorial material for self-hosted deployments.
Dependency audits, SBOM updates, validation hardening, and responsible disclosure handling.
Keeping pace with Java, Vaadin, Hugo, dependency updates, and release hygiene.
Platforms
GitHub Sponsors
Preferred for recurring support. Monthly tiers from small individual support to visible project backing.
Ko-fi
Simple one-time donations or small monthly support without a heavy process.
Open Collective
Transparent funding flow with bookkeeping and invoices for organizations.
Recognition
Sponsorship is voluntary support for the open-source project. Recognition is intentionally simple: names, logos, and priority labeling for supporters who help keep the project moving.
| Perk | Coffee | Supporter | Backer | Logo |
|---|---|---|---|---|
| Name in README | yes | yes | yes | yes |
| Name on website | no | yes | yes | yes |
| Logo in README | no | no | yes | yes |
| Logo on website | no | no | no | yes |
| Priority issue labeling | no | no | yes | yes |
| Prioritized feature requests | no | no | yes | yes |
| Top-priority feature handling | no | no | no | yes |
| Monthly progress update | no | no | no | yes |
Sponsored feature requests
Sponsors at the Backer tier or higher can submit feature requests that are reviewed and prioritized against the regular backlog. Submit through GitHub Sponsors messages or via the contact channel listed in the project repository.
Describe the use case, expected behaviour, and how it would be deployed. Concrete scenarios beat abstract wishes.
Each request is reviewed against project scope, maintenance cost, security implications, and existing roadmap.
One of three outcomes — integrated into the open-source core, offered as a separate module, or transparently declined with reasoning.
Decision policy
Sponsorship buys priority review and a clear answer, not a guarantee that every request lands in the core. The goal is a coherent product that stays maintainable for everyone.
| Outcome | What it means |
|---|---|
| Core | Fits the open-source scope and benefits all users — merged into the EUPL-1.2 edition. |
| Module | Useful but out of core scope — offered as a separate module (open or commercial, case by case). |
| Decline | Conflicts with project direction, security model, or maintenance budget — declined with written reasoning. |
Current sponsors
Names and logos can be shown here once sponsorship tiers are active.
FAQ
Yes. The open-source edition is licensed under the EUPL-1.2 and remains free. Sponsoring is voluntary support for continued development.
Use Open Collective for transparent bookkeeping and company-friendly invoices.
Use the logo sponsor tier and send the logo details through the contact channel listed in the project repository.
No. Sponsoring at the Backer tier or higher buys prioritized review and a clear decision. Each request can be merged into the core, offered as a separate module, or declined with written reasoning.
You receive an explanation grounded in project scope, security, or maintenance cost. Declined requests do not reduce or refund sponsorship — sponsorship supports the project as a whole, not a single feature.
Send the request through your GitHub Sponsors message channel or via the contact details in the project repository. Concrete use cases and deployment context speed up the review.