Sponsor
Sponsor Security for Flow
Security for Flow is developed in the open under EUPL 1.2. There is no company behind it — just one engineer who maintains it alongside client work. Sponsoring is what keeps the lights on for new features, security hardening, and timely releases.
What your sponsorship pays for
- Security hardening —
LoginAttemptPolicy,SessionPolicy,SecurityAuditService(see the Roadmap). - Faster turnaround on bug reports and CVE-class issues.
- Maintenance of the reference demos against new Vaadin and JDK versions.
- Documentation, blog posts, and conference talks that bring more contributors in.
For individuals
The simplest way: GitHub Sponsors. Monthly or one-off, public or private, cancel any time.
For companies
If your company depends on Security for Flow, dedicated corporate sponsorship is the most impactful way to support it.
| Tier | What you get |
|---|---|
| Bronze | Logo and link in the README and on this site. Acknowledgement in release notes. |
| Silver | All of Bronze, plus quarterly office-hours call and priority issue triage. |
| Gold | All of Silver, plus a named contact channel, roadmap input, and a guaranteed monthly response window. |
Tiers are intentionally not priced publicly — the right number depends on your company size and what level of involvement makes sense.
Discuss corporate sponsoring: contact@sven-ruppert.com
I’ll reply with payment options (invoice, bank transfer, Open Collective Europe), tier details, and a sponsor agreement template.
What sponsoring is not
- It is not a paid support contract. For dedicated, SLA-backed work on your codebase, see Consulting instead.
- It does not influence the open-source license. Security for Flow stays EUPL 1.2 — sponsorship buys gratitude and roadmap influence, not exclusivity.
Thanks
To everyone who has filed an issue, sent a PR, or quietly run the library in production: thank you. The project exists because of you.