PocketBase Funding Falls Through: What This Means for Open Source Sustainability

Last week, PocketBase creator Georgi Ganev announced something that hit the open source community like a cold shower: a much-anticipated FLOSS/fund sponsorship had fallen through. The funding—announced with fanfare just months ago—would have let him work full-time on PocketBase for a year. Instead, regulatory hurdles and concerns about data handling in India forced him to walk away.

It’s a story that’s become far too familiar in the open source world.

What Happened

If you missed it, here’s the quick version: FLOSS/fund (a platform that connects open source projects with sponsors) had selected PocketBase for their second funding tranche. The sponsorship was announced publicly in December 2025. Ganev even made plans based on that income, talking about rewriting the PocketBase dashboard UI and finally pushing toward a stable 1.0 release.

Then everything fell apart.

According to Ganev’s update, FLOSS/fund wanted to issue a wire transfer from India, requiring “cross-jurisdictional paperwork” that involved sharing sensitive personal data through “insecure shared mail inbox channels.” He wrote that he “didn’t feel comfortable” with the arrangement and withdrew from the program.

The funding never materialized.

This Isn’t Unusual—And That’s the Problem

Here’s what got me: the Hacker News discussion underneath the announcement was filled with maintainers sharing their own horror stories. One person mentioned a VC firm that promised funding, made them sign papers, then went silent for months before ghosting entirely. Another talked about a corporate sponsor that wanted “exclusive rights” as part of the deal—something completely at odds with open source licensing.

The pattern is depressingly consistent: promises are made, announcements are published, and then… nothing. Or worse, the money comes with strings that undermine the very philosophy that makes open source work.

Ganev admitted this himself: “I made a mistake for not researching it more carefully and not waiting for the disbursal before making big announcements and decisions.”

Ouch. But he’s right. And it’s a lesson that costs more than just embarrassment—it affects real people’s livelihoods.

What PocketBase Will Do Now

Despite the setback, the project isn’t dying. Ganev has confirmed:

• The UI rewrite is already partially implemented
• PocketBase will continue with the goal of a stable release “this year” (no hard promises)
• The project enters a temporary “feature freeze” while he focuses on the dashboard
• He’s still looking for alternative funding

He’s also created a new frontend framework called Shablon—zero dependencies, plain JavaScript—to avoid the complexity of maintaining a Svelte-based UI. It’s an elegant solution to a real problem, but it’s also a reminder of how much extra work maintainers do when funding falls short.

What This Means for the Open Source Ecosystem

This incident highlights several uncomfortable truths:

1. Open source funding is fragile

A single funding source—even a legitimate one—can collapse due to factors completely outside the maintainer’s control. Regulatory issues, corporate politics, or simple bad timing can derail months of planning.

2. Announcing too early hurts

We’ve all seen the blog posts: “Excited to announce we’re getting funding!” Only for that funding to never materialize. It’s tempting to share good news early, but it sets expectations that can backfire badly.

3. Diversification matters

The old advice holds: don’t rely on a single funding source. Patreon, GitHub Sponsors, consulting, SaaS tiers, corporate sponsorships—spread the risk. If one falls through, you survive.

4. Community is the backup

In the discussion thread, several people said they’d be willing to support PocketBase directly through GitHub Sponsors or Patreon. The community that uses your project can be a safety net when institutional funding fails. But only if you’ve built that relationship.

The Bigger Picture

Let’s be honest: PocketBase is one of the lucky ones. It’s a popular project with a strong community and a dedicated maintainer. Even without the FLOSS/fund money, it’ll probably survive.

But what about the thousands of smaller projects that don’t have that luxury? The ones where a single funding collapse means the project simply dies?

That’s the question we should be asking. Not just “how do we fund open source” but “how do we make that funding reliable?”

What Maintainers Can Learn

If you’re running an open source project, here’s what this situation teaches us:

1. Don’t announce funding until the check clears. It feels good to share good news, but premature announcements create pressure that makes pivots harder.

2. Read the fine print. Regulatory issues, jurisdiction concerns, and data handling can kill deals. Have a lawyer look at anything involving cross-border transfers.

3. Build community relationships early. The time to ask for support is before you need it. Engage with your users, respond to issues, and create a sense of ownership.

4. Keep your day job (or don’t quit it). Until funding is 100% certain, maintain financial stability. The dream of full-time open source is great until reality intervenes.

5. Consider multiple revenue streams. GitHub Sponsors, Open Collective, Patreon, consulting, and commercial licensing can all contribute. No single source should represent more than maybe 30-40% of your income if you can help it.

What’s Next for PocketBase

Despite everything, Ganev seems determined to keep going. The UI rewrite using Shablon is underway, and he’s asked for patience as he works through the remaining tasks.

It’s a reminder that open source maintainers are human. They get excited, they make mistakes, they face setbacks. What matters is whether they keep going.

I’ll be watching to see how this plays out. And if you’re a PocketBase user, now might be a good time to contribute—whether through code, documentation, or financial support.

The project deserves to succeed. Let’s make sure it can.

---

Have you experienced funding issues with open source projects? Or have advice for maintainers? Let’s discuss in the comments below.