Funding areas

Where sponsorship money goes.

Support is directed at practical project work that makes the software easier to run, inspect, and trust.

New features

Persistence improvements, authentication layers, deployment packaging, and sponsor-driven feature requests.

Documentation

More guides, API examples, diagrams, and tutorial material for self-hosted deployments.

Security reviews

Dependency audits, SBOM updates, validation hardening, and responsible disclosure handling.

Maintenance

Keeping pace with Java, Vaadin, Hugo, dependency updates, and release hygiene.

Platforms

Choose the sponsorship channel that fits your workflow.

Recognition

Sponsor perks stay useful and transparent.

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.

Sponsored feature requests

Shape the roadmap from the Backer tier upward.

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.

1. Submit

Describe the use case, expected behaviour, and how it would be deployed. Concrete scenarios beat abstract wishes.

2. Review

Each request is reviewed against project scope, maintenance cost, security implications, and existing roadmap.

3. Decision

One of three outcomes — integrated into the open-source core, offered as a separate module, or transparently declined with reasoning.

Decision policy

Three possible outcomes — and the maintainer makes the call.

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

Public sponsor area.

Names and logos can be shown here once sponsorship tiers are active.

Be the first sponsor Your name or logo can appear in this section.

FAQ

Common sponsorship questions.

Is URL Shortener still free if I do not sponsor?

Yes. The open-source edition is licensed under the EUPL-1.2 and remains free. Sponsoring is voluntary support for continued development.

Can my company get an invoice?

Use Open Collective for transparent bookkeeping and company-friendly invoices.

How do I get my logo on the website?

Use the logo sponsor tier and send the logo details through the contact channel listed in the project repository.

Does sponsoring guarantee my feature lands in the core?

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.

What happens if my feature request is declined?

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.

How do I submit a feature request as a sponsor?

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.