Baserow Is Moving from GitLab to GitHub

TL;DR

We’re moving Baserow’s primary development from GitLab to GitHub to improve visibility, reach more open-source contributors, and simplify collaboration. While GitLab has served us well — and we remain strong supporters of its mission — we believe GitHub offers greater discoverability and long-term growth for our community. All future issues, pull requests, and releases will be managed on GitHub. The GitLab repo will remain as a read-only mirror.

⭐️ Follow and star us on GitHub

At Baserow, we believe in building in the open. As a fully open-source platform, our community, contributors, and developer experience have always been central to our growth.

Since day one, we’ve hosted our source code on GitLab — a platform that aligns closely with our own open values. GitLab has served us well, and we remain strong supporters of its mission and contribution to the open-source ecosystem.

But after careful consideration, we’ve decided to transition Baserow’s primary development activities to GitHub.

This is not a decision we made lightly. In fact, it is rooted in one simple question:

Are we missing out on discoverability and collaboration by not being where most developers already are?

Open Source Is About Community — And Community Lives on GitHub

GitHub has become the default hub for open-source collaboration.

To put this into perspective:

• The most starred open-source project on GitLab, which is GitLab itself, currently has around 7,100 stars
• The most starred project on GitHub, freeCodeCamp, has over 430,000 stars

While Baserow is currently ranked as one of the top 10 most-starred projects on GitLab, we believe there’s a much larger audience we haven’t yet reached, simply because we’re not as visible on GitHub.

We want developers to discover Baserow more easily. We want contributors to be able to fork, test, and build with us using the tools and workflows they already know. And we want to reduce the friction for teams who are already active on GitHub and looking to adopt or contribute to Baserow.

What Will Change (and What Won’t)

As part of this transition, we will begin managing the following directly on GitHub:

• Issues and bug tracking
• Pull requests and merge workflows
• Continuous integration pipelines
• Releases and changelogs
• Contributor discussions

Our GitLab repository will remain active, but in a read-only mirror mode. This ensures nothing breaks for existing users or builds, while clearly signaling where future development is happening.

Why This Matters for the Baserow Community

We know many of you found us through GitLab. If you’re using Baserow in self-hosted deployments, CI/CD pipelines, or have starred us as a favorite project — we’re incredibly grateful.

We are not turning our back on GitLab. We’re simply moving our main development home to GitHub in order to grow the project further, collaborate more widely, and meet our open-source goals with a broader community.

This move reflects where the ecosystem is today, and where we believe the most impact can be made going forward.

Help Us Build in the Open — On GitHub

You can now follow and star the Baserow repository on GitHub here.

If you’re a developer, contributor, plugin builder, or just curious about the project — we invite you to join us there. Every star, issue, or pull request helps us build better, together.

As always, we remain committed to transparency, community, and openness. This migration will help us scale those values further by aligning with where the global open-source community already collaborates.

Thank you to the GitLab team for supporting the open-source movement. And thank you to our community for continuing to help us shape the future of no-code.

We’ll see you on GitHub. 👋