Back the library
your code relies on.
functional-reactive is developed in the open by one engineer alongside client work. Sponsorship is what keeps the lights on for new features, maintenance against new JDKs, and timely releases.
Four concrete things your sponsorship buys
Not a black box. Sponsorship pays for the work already on the roadmap and the steady-state maintenance that keeps the library production-grade.
JDK compatibility
Keeping the library green across JDK 8, 11, 17, 21 and every new LTS. Tedious work, more important than features.
Faster issue turnaround
Bug reports and regression issues get triaged in days, not weeks. Sponsors get priority on the queue.
New features
Records-based tuples shipped; pattern-matching Case
polish, structured concurrency adapters, and more on deck.
Outreach & docs
Tutorials, blog posts, and conference talks that bring more contributors in. A bigger ecosystem benefits everyone running the library.
GitHub Sponsors — one click, any tier
- ✓ Thank-you in the README
- ✓ Direct line for feedback & feature requests
- ✓ That "I made open source possible today" feeling
Three tiers, monthly billing
Coffee-price to small-team scale. Billed through GitHub Sponsors, cancel any time. Perks compound: each tier includes everything below it.
€10/month
Individual supporter tier — say "thanks, keep going" for the price of a coffee.
- ✓ Thank-you in the README
- ✓ Listed in release notes
- ✓ That "I made open source possible today" feeling
€50/month
Small-team tier — most companies running the library in production land here.
- ✓ Everything in Bronze
- ✓ Name / logo + link on the project README
- ✓ Priority issue triage (within 5 business days)
€100/month
Business tier — for teams that want a working line of communication.
- ✓ Everything in Silver
- ✓ Logo on the project homepage
- ✓ Dedicated email channel for questions
- ✓ One 30-min Q&A call per quarter
Billed monthly through GitHub Sponsors. EU VAT handled by GitHub.
Corporate sponsorship
If your product relies on functional-reactive in production, corporate sponsorship turns "we hope it stays maintained" into a working line of communication with the maintainer — plus tangible value-adds your engineering and legal teams will use.
€5,000/year
For teams under ~50 engineers shipping the library in production.
- ✓ Logo on README, homepage and docs
- ✓ Priority bug triage (within 2 business days)
- ✓ Early access to security advisories
- ✓ One 60-min advisory call per quarter
- ✓ Named in release notes for the year
- ✓ Signed dependency & license attestation letter
€15,000/year
For product companies with multiple services depending on the library.
- ✓ Everything in Startup
- ✓ Prominent logo placement on homepage
- ✓ Dedicated Slack / email channel (24-hour response, business days)
- ✓ Roadmap input — recorded in public issues
- ✓ Monthly office hour (30 min)
- ✓ Pre-release builds (preview before public tag)
- ✓ Two training-credit hours per quarter (any topic)
Custom
For platforms shipping functional-reactive to many downstream customers.
- ✓ Everything in Business
- ✓ Custom SLA with same-day response for production-blockers
- ✓ Reserved engineering days per quarter (sponsored features)
- ✓ Long-term support branch maintenance for your JDK target
- ✓ Co-marketing on case studies (optional)
- ✓ Annual on-site or remote engineering workshop (2 days)
- ✓ Quarterly architecture review & threat-model walkthrough
All corporate tiers include
What sponsorship does not change
License stays EUPL 1.2
No bait-and-switch to a proprietary or "source-available" license. EUPL 1.2, permanently, for everyone.
Public roadmap
Sponsor input is recorded in public issues. No back-channel decisions that shape the codebase without the community seeing them.
No lock-in
Cancel any time. Drop the dependency any time. The library is small enough to fork — and I'd rather you have that option than feel trapped.
Every contribution counts
Individuals & small teams use GitHub Sponsors — quick, monthly, cancel any time.
Companies reach out by email for annual corporate sponsorship with SLAs and roadmap input.