- Updated: February 18, 2026
- 5 min read
PocketBase UI Rewrite Discussion Highlights
PocketBase’s recent community discussion revealed a major UI rewrite using the custom‑built Shablon framework and the unexpected withdrawal of a FLOSS/fund sponsorship due to cross‑border regulatory issues.
Overview of the PocketBase Community Discussion and Funding Announcement
On October 28 2025, the maintainer of PocketBase’s GitHub discussion announced a partnership with FLOSS/fund that would have provided a year‑long financial runway for a stable release. The announcement generated a flurry of excitement across the open‑source backend community, as developers anticipated faster feature delivery and a more polished admin UI.
The funding was meant to cover full‑time development, documentation upgrades, and a comprehensive UI overhaul. However, the same thread later disclosed that the sponsorship was retracted because of “unforeseen regulatory constraints” tied to cross‑jurisdictional wire transfers from India. This twist sparked a second wave of discussion focused on the sustainability of community‑driven financing for open‑source projects.
Details of the Planned UI Rewrite with Shablon
The core of the UI rewrite revolves around a brand‑new front‑end framework called Shablon. Unlike mainstream libraries such as Vue or React, Shablon is a zero‑dependency JavaScript toolkit that manipulates plain DOM nodes directly. Its design goals align perfectly with PocketBase’s philosophy of keeping the stack lightweight and easy to maintain.
Why Shablon Over Existing Frameworks?
- Zero external dependencies → smaller bundle size and fewer breaking changes.
- Plain‑JS API eliminates the need for a separate build step, simplifying plugin development.
- Fine‑grained control over the SPA router and reactivity states, essential for a customizable admin dashboard.
The maintainer explained that existing frameworks like Svelte, Vue, or Lit introduce “runtime overhead and frequent major version upgrades that could break custom UI plugins.” By building Shablon from scratch, the project can lock the UI layer for the foreseeable future, ensuring that the stable release remains truly stable.
Key Features of the New UI Kit
- Modular field components (text, number, date, file) that can be extended via simple JavaScript functions.
- Themeable design system with light/dark modes and a “production‑mode” visual cue.
- Responsive layout that adapts to mobile screens without additional CSS frameworks.
- Built‑in plugin hooks allowing developers to inject custom actions into the dashboard.
“The majority of the new UI functionality is already implemented; Shablon is now 90 % complete and consists of fewer than 600 lines of code.” – GitHub discussion
Community Reactions and Feedback
The announcement elicited a spectrum of responses from the PocketBase user base:
- Optimism: Many developers praised the move toward a fully extensible UI, noting that “custom dashboards have been a long‑standing pain point.”
- Skepticism: Some community members warned that a home‑grown framework could become a maintenance burden if not documented thoroughly.
- Supportive suggestions: Contributors offered alternative libraries (e.g., HTMX, Templ) and shared early prototypes for UI plugins.
Overall, the sentiment remains positive, with the majority of commenters expressing confidence that the new UI will unlock advanced use‑cases such as custom OAuth providers, dynamic field renderers, and real‑time collaboration tools.
Reasons for Funding Withdrawal and Regulatory Concerns
The funding reversal stemmed from a combination of legal and security considerations:
- Cross‑jurisdictional wire transfer: FLOSS/fund proposed a transfer from India, which required extensive paperwork and raised data‑privacy questions.
- Data‑sensitivity: The maintainer expressed discomfort with routing personal and project‑related data through an insecure shared‑mail channel.
- Compliance risk: Potential exposure to Indian financial regulations could have conflicted with the open‑source project’s global contributor base.
In a candid follow‑up post, the maintainer admitted that the premature announcement was a misstep, but reaffirmed the commitment to delivering a stable version of PocketBase regardless of external financing.
Future Roadmap and Commitment to Stable Releases
Even without the FLOSS/fund injection, the development timeline remains aggressive:
- Complete Shablon integration: Final polishing of the UI kit, mobile responsiveness, and theme support.
- Publish a migration guide: Step‑by‑step instructions for moving from v0.22.x to the upcoming stable branch.
- Feature freeze: A temporary pause on new backend features to focus on UI stability and documentation.
- Bi‑annual Go releases: Align future PocketBase releases with the Go language’s stable cycle to minimize breaking changes.
The maintainer also hinted at exploring additional revenue streams, such as a partner program or premium support, to ensure long‑term sustainability without compromising the project’s open‑source ethos.
How UBOS Can Complement PocketBase Development
Developers looking to extend PocketBase’s capabilities can leverage the UBOS platform overview for rapid prototyping. UBOS offers a suite of low‑code tools that integrate seamlessly with open‑source back‑ends:
- Web app editor on UBOS – drag‑and‑drop UI builder that can consume PocketBase APIs.
- Workflow automation studio – design automated data pipelines without writing boilerplate code.
- UBOS templates for quick start – ready‑made templates such as AI SEO Analyzer or AI Article Copywriter that can be hooked to PocketBase collections.
- AI marketing agents – automate campaign creation using data stored in PocketBase.
For startups, the UBOS for startups page outlines a cost‑effective path to launch MVPs, while SMBs can explore UBOS solutions for SMBs that include built‑in authentication, analytics, and multi‑language support.
Conclusion & Call‑to‑Action
PocketBase’s journey illustrates both the promise and the pitfalls of community‑driven funding. The UI rewrite with Shablon promises a more extensible, lightweight admin experience, while the funding setback underscores the need for transparent, jurisdiction‑aware sponsorship models.
If you’re a developer eager to experiment with the new UI or contribute to the migration guide, now is the perfect time to get involved. Join the discussion, test the AI Video Generator template, or explore the Enterprise AI platform by UBOS for larger deployments.
Stay updated on PocketBase’s roadmap by bookmarking the official GitHub discussion and following the UBOS open‑source blog. For hands‑on learning, check out the developer guides that walk through API integration, authentication, and UI customization.