The problem we keep seeing
Every new project starts the same way. You need a database. You need an admin panel. You need authentication, an API layer, file storage, permissions. You've built all of this before — maybe dozens of times. And yet, every time, you start from scratch or lock yourself into a platform that owns your data and your roadmap.
The cloud platforms made it easy. Firebase, Supabase, the managed CMS tools — they let you skip the plumbing and get to building. But ease came with a price: vendor lock-in, opaque pricing, data you can't fully control, and an architecture you can't truly own.
On the other side, self-hosted tools exist, but they often feel like a different era. They're hard to set up, painful to customize, and designed for a world before AI, before TypeScript-everywhere, before developers expected tools to just work.
Where we come from
We're not new to this. Before Rebase, we built FireCMS — an open-source CMS for Firebase that's been used in over 10,000 projects worldwide, trusted by teams at companies like Microsoft and IKEA. We spent years learning what developers actually need from an admin panel, what content editors struggle with, and where every CMS eventually breaks down.
FireCMS taught us a lot. It taught us that developers want flexibility, not lock-in. That end users want beauty and simplicity, not a wall of forms. That the best tools disappear into the background and let people focus on their actual work.
But FireCMS was tied to Firebase. And as we watched the industry move toward Postgres, toward open standards, toward data sovereignty — we knew it was time to build something bigger. Something that could be the foundation for any digital project, not just those on one cloud provider.
What we believe
Open source is not a feature — it's a foundation
Rebase is fully open source under the MIT license. Every package, every line of code. Not open-core with a bait-and-switch. Not source-available with restrictions. MIT — because we believe the infrastructure you build on should truly be yours.
Self-hosting should be as easy as using a cloud service
If setting up your own instance takes more than a few minutes, we've failed. Rebase should be as frictionless to deploy as signing up for a SaaS. Docker, Railway, Fly, bare metal — wherever you want to run it, it should just work.
Your database is your truth
We don't create shadow databases. We don't abstract your schema away behind proprietary layers. Rebase connects directly to your Postgres, reads your tables, and builds on top of what you already have. Your data never leaves your infrastructure.
From weekend project to enterprise — on the same platform
We want Rebase to be what you reach for on a Saturday afternoon hack and what you deploy in production on Monday. The same tool for a solo developer prototyping an idea and for a team of fifty managing a complex internal platform. No artificial ceilings, no upgrade-to-unlock walls.
The repetitive parts should not exist
Setting up an admin panel, writing CRUD endpoints, wiring authentication, building form validation, configuring file storage — this is solved-problem territory. You shouldn't spend another week on it. Define your schema, and let the platform generate the rest.
Europe needs its own infrastructure
We're building Rebase from Europe, and we care deeply about data sovereignty, GDPR compliance, and digital independence. But this isn't just a European project — it's for anyone who believes their data should stay where they put it.
Who is Rebase for
Rebase is for anyone who's tired of choosing between ease-of-use and ownership:
- The developer who wants Firebase-like speed without Firebase-like lock-in
- The startup that needs to move fast today and scale tomorrow — without re-platforming
- The agency that's tired of rebuilding the same admin panel for every client project
- The enterprise team that needs to keep data on their own infrastructure, with full audit trails
Rebase is highly modular — use the admin panel, the API layer, the SDK, or the full platform. Take only the parts you need, leave the rest. You decide how much of the stack you adopt.
Built for three worlds
Most tools are designed for one audience. We're building for three — because we believe the best platform is one where everyone can work effectively:
End Users
Beautiful, intuitive interfaces that non-technical people actually enjoy using.
Developers
TypeScript-native, React-extensible, with APIs and SDKs that feel like they were made for you.
AI Agents
MCP server, structured APIs, and machine-readable schemas — so agents can build with Rebase too.
Our promise
We're not building Rebase to flip it or to lock you in. We're building it because we've spent our careers making developer tools, and we know this is what's missing: an open, beautiful, Postgres-native platform that respects your data, your time, and your intelligence.
We ship fast. We listen to our community. We believe in building in public. And we're just getting started.
If any of this resonates with you — if you've felt the same frustration, if you believe the same things — come build with us.
The Rebase Team
Madrid · Building in the open since 2020
