Sponsor
Where sponsorship goes, what each tier carries, and the other ways to help.
Where it goes
quello is free and MIT-licensed, and it will stay that way. It is maintained by one person, and most of the work now is upkeep: eleven playgrounds that have to keep agreeing with the compatibility matrix as Vite, webpack, Next, Nuxt, Astro and the rest keep changing.
Sponsoring helps cover the time that takes. If you decide to, thank you — at this size it makes a real difference.
Sponsor quello on GitHubWhat each tier carries
The amounts are on the sponsors page.
| Tier | Where you appear |
|---|---|
| Supporter | Your name on this page and in SPONSORS.md. |
| Backer | Your name and a link, in both, and in the README. |
| Partner | Your logo and a link in all of the above, plus the docs homepage. |
A one-time sponsorship is just as welcome; it simply does not come with a listing.
Worth saying up front rather than leaving it implied: sponsoring does not come with priority or
private support, and the issue tracker stays first-come for everyone. It goes toward the upkeep.
Current sponsors
No sponsors yet. If you are the first, thank you.
Other ways to help
Money is not the only way, and at 0.1.x it may not even be the most useful one:
- Tell me what broke. A pick that resolves to the wrong component, on a framework version I have not tried, is genuinely useful.
- Add a row to the matrix. Rails, Laravel, Ember, Qwik — the CLI route should
already work, and a confirmation from a real project turns a
○into a✅. - Mention it. A line in an awesome-list, or a word where your team talks about tooling, goes a long way.