Why I am exploring sponsorship
I've been building open-source tools for developers for a little over two years, in the spare time I find between other obligations.
It has worked so far, but it has an obvious limit: the time I can dedicate to it always competes with everything else.
That's why I'm exploring sponsorship.
In this article I'll cover:
- Why sponsor?
- My work in numbers
- My commitment
Why sponsor?
I'm sure that at some point you've used a library or tool that saved your life, but when checking the date of the last commit, you noticed it was five years ago.
This happens constantly because the free and open-source software model is hard to sustain, and with the arrival of AI models, it has become even more complicated. If you need an example, just recall the Tailwind CSS drama in early 2026.
I would like to dedicate myself full-time to building tools for developers while also preventing my projects from ending up abandoned. I want them to be stable projects, with constant updates, ones that developers can rely on.
To achieve this, sponsorship is the first step.
My work in numbers
I'm not going to pretend my stats are Evan You's or that my projects are used by S&P 500 companies.
So far, my packages are installed a little over 500 times per week according to npmx, and in total they have accumulated 195 stars on GitHub. These are modest numbers, but they are real and they are growing.
I mention them because I think you deserve to know exactly where I stand before deciding whether to sponsor me. I'm not an established project looking for more funding: I'm an independent developer at an early stage, and your sponsorship would make a real difference.
My commitment
Everything that is already open-source will remain so, and I will continue releasing more projects under that model. The same applies to paid tools: they will always have a one-time payment option with lifetime access, no forced subscriptions or surprise model changes.
I believe developers deserve tools they can rely on long-term, and that starts with being predictable and transparent in the way I manage my projects.
I want to be clear: even though this is a sponsorship, I see it as a business relationship in which you are my client. That means your feedback matters, I am committed to delivering real value, and this is not simply about donating money.
This is what I offer:
- Full access to SEO in Next.js, SEO in Astro, and any future private libraries and tools I develop
- Early access to new libraries, tools and features before public release
- Feature requests and bug reports prioritized for private and open source projects
Nobody knows better than you what you need. If there is something you would find valuable (tools, content, specific resources, etc.) just let me know and we will find the best way to make it possible.
If this resonates with you, consider sponsoring my work.
Final reflections
Sponsorship is one way to support me, but it's not the only one.
If your company has a budget for tools or training, which is more common than it seems, it can be a way to justify the expense without it coming out of your own pocket.
And if sponsorship is not for you, there are other equally valuable ways: buying one of my paid tools, leaving a star on GitHub, or simply sharing the project with someone you think might find it useful.
Every bit helps.