Tabularis Joins the Vercel Open Source Program
A short while after DigitalOcean welcomed us into their Open Source Credits Program, we got another email we weren't expecting: Tabularis has been accepted into the Vercel Open Source Program, in the Spring 2026 cohort.
We'll be honest about our bias here: we're genuinely fans of Vercel. We've followed the platform and its products for years, and a fair amount of how we think about shipping the web — fast previews, sane defaults, treating the deploy as part of the developer experience rather than an afterthought — has Vercel's fingerprints on it. So being picked is not a polite "thanks for applying." It's getting a nod from a team whose work we already admired. We're genuinely honored.
The terms are refreshingly simple. Stay fully open source, deploy on Vercel, keep a badge in the README for twelve months. That's it. No equity, no roadmap strings, no quarterly check-in deck. For a project that's still run on nights and weekends, an email that says "we like what you're doing, here's a year of support, carry on" is a rare kind of thing.
The part that makes this one different
The DigitalOcean credits go toward infrastructure for the plugin registry — backend, the stuff users never see directly. The Vercel support lands somewhere more visible, and frankly more fun to talk about.
This site is the thing being supported. tabularis.dev — the page you're reading this on, the wiki, the changelog, the plugin pages — is a Next.js app, it's open source, and it's the front door to everything else we build. The download links, the docs people land on from a Google search, the release notes that go out every couple of weeks: all of it runs through here.
So this isn't "a sponsor pays for our servers" in the abstract. It's the tooling we use to talk to you, getting a real upgrade. There's something fitting about an open-source database client having an open-source website, both supported by the same kind of program. The whole stack, all the way down, is something you can read, fork, and send a PR to.
What we're actually going to do with it
We're not going to pretend a year of Vercel turns the site into something it isn't. But there's a backlog of things that have been "later" for too long, and "later" just became "now":
- Faster previews on every content change. Most of what we ship here is Markdown — blog posts, wiki pages, comparison pages. Preview deployments mean we can see a post rendered, OG card and all, before it goes live. Fewer typos shipped to production.
- A site that keeps up with the app. Tabularis ships roughly every two weeks. The site has to keep pace — new features documented, the changelog current, the plugin pages accurate. Better build and deploy tooling makes that less of a chore and more of a habit.
- The boring-but-important stuff. Performance, the search index, the things that make the docs actually findable. None of it is glamorous. All of it is what makes a project feel maintained rather than abandoned.
If you've got an idea for what the site should do better, the repo is right there. Issues and PRs are open.
Finding Tabularis useful? Star it on GitHub — it takes a second and helps more developers discover the project. Star on GitHubThanks, and the usual honest note
To Amy and the team running the Vercel Open Source Program: thank you. Picking a young project out of a stack of strong applications is a vote of confidence, and we don't take it as a given.
To everyone who's starred the repo, filed a bug, shipped a plugin, translated a string, or just told a colleague about Tabularis: this is the kind of thing that happens because a project looks alive, and a project looks alive because of you. Two sponsorships in two months isn't luck. It's the curve you've all been bending upward.
We'll be sharing this across our channels over the next few days. If you want to help it travel, that's the best thank-you we could ask for.
The road ahead is the longest part. We're glad you're on it with us.
The Tabularis Team