The Postgres you already have.
The backend you always wanted.
Point Rebase at your database and get REST APIs, auth, storage, realtime — and an admin panel when you want one. Secured by Postgres row-level security, not middleware. Ready for your team and your AI agents.
Prefer your terminal? Up and running locally in under a minute:
See it for yourself
From connection string to control panel
APIs, auth and realtime are running the moment you connect. This is the back office that comes with them — generated, not built.
A quick tour of the generated Rebase admin panel.
The backend underneath
A full backend. Not just a pretty face.
The admin panel is the layer you see. Underneath it: a typed SDK, instant REST, and realtime over WebSocket — running against your database from minute one.
TypeScript SDK
Fully type-safe SDK with IDE auto-complete. Schema changes update your types automatically.
Instant REST API
Your schema generates secure REST APIs — auto-generated, zero boilerplate.
Realtime engine
Live data subscriptions, broadcast channels, and presence tracking — all over WebSocket. Build chat, dashboards, and collaborative UIs without any extra infrastructure.
Modular by design
Adopt only what you need.
Three modes, same packages, wired differently. Start headless, add the admin panel later — or never. Nothing is bundled that you didn't ask for.
BaaS — just the backend
REST, auth, storage, realtime and backups over your database. No config files, no UI, no React in the dependency tree. Every protected table is served automatically, straight from your schema.
CMS — add the admin panel
Define collections in TypeScript and get a schema-driven back office: spreadsheet editing, media, workflows — extensible with your own React components.
Full — add the Studio
SQL editor, schema visualizer, RLS policy editor, logs and API explorer on top of everything else. The whole platform, one self-hosted app.
Your schema, your rules.
Row-level security defined right in your TypeScript schema. Granular permissions per collection, per field, per role. No hand-written SQL policies — just clean code that lives in version control.
Your code. Your infra.
Zero lock-in.
MIT-licensed. Self-host on Docker, Railway, Fly, or bare metal. Your data stays in your Postgres — no vendor dependency, no surprises, no per-seat pricing.
Built for the agent era
The backend an agent can't screw up
An AI agent can scaffold a backend in an hour. It can't tell you whether that backend is safe. Agents are extremely good at producing plausible backends — and famously bad at producing secure ones. Rebase makes the safe outcome the only outcome, by construction.
Fail-closed by construction
Authorization in Rebase is Postgres row-level security, enforced by the database itself — not by hoping the agent wrote good middleware. A table without RLS is never served. There is no auth check to forget, so there is nothing your agent can forget to write.
Agent-native, not agent-washed
A built-in MCP server with real tools — data CRUD, users, migrations, cron, schema introspection — plus twenty packaged agent skills for Claude, Gemini, Kiro and anything else that speaks the protocol. Your agent doesn't scrape the docs; it operates the platform.
Humans keep the back office
Agents write data faster than anyone can read it. The admin panel is the piece they don't replace: a place for people to inspect, correct and approve what their agents are doing — generated from your schema, extensible in React.
Boilerplate depreciates. Guarantees appreciate.
Agents made day-one code cheap. What stayed expensive are the day-30 problems: RLS correctness, backups, migrations, realtime consistency. Rebase isn't the boilerplate your agent would have written anyway — it's the operational guarantees it can't.
Built for Real Products
Teams Ship Faster with REBASE
From marketplaces to SaaS platforms and internal tools, Rebase eliminates the glue code between database, API, and UI.
MedicalMotion
A certified digital medical device (app) using AI to provide personalized holistic pain therapy. Rebase powers everything behind the scenes, from patient data management to clinical tracking and content delivery.
Secure Patient Data
Medical patient profiles, therapy plans, and sensitive health records are stored securely, with row-level security configured via the Rebase schema.
Content Delivery
Rebase delivers the daily therapy plans, physiotherapy video exercises, and educational content seamlessly through generated APIs.
Clinical Tracking
Internal teams use the Rebase admin panel to monitor app engagement, manage the exercise library, and generate health reports.
SustenTalent
A dual-sided talent marketplace connecting sustainability professionals with green companies. Built entirely on Rebase, SustenTalent handles complex role-based routing, user profiles with multiple roles, and thousands of job postings.
Dual-Role Authentication
Leveraged Rebase auth to allow users to hold both 'talent' and 'company' profiles simultaneously, with automatic dashboard redirection.
Generated Data APIs
Used the auto-generated TypeScript SDK to securely fetch matched job vacancies based on professional interests, ensuring full type safety in their frontend app.
Out-of-the-box Admin
The staff uses the generated Rebase admin panel to moderate job postings, verify companies, and manage the proprietary interests taxonomy.
Frequently asked questions
What database does Rebase support?
PostgreSQL is the primary focus — Rebase goes deep on Postgres so every feature (RLS, enums, constraints, relations) works natively. That said, the architecture is database-agnostic and can be adapted to other databases. You bring your own database instance; Rebase never hosts or copies your data.
How is Rebase different from Retool or Supabase?
Unlike Retool, Rebase is open-source with no per-seat pricing lock-in, and it's a real React framework you can extend with your own code. Unlike Supabase, Rebase connects directly to your existing Postgres database — no new infrastructure to manage, no vendor-managed instance. Your schema, your data, your rules.
Can I use Rebase with an existing database?
Absolutely. Point Rebase at any Postgres connection string and it will read your tables, columns, foreign keys, enums, and constraints to generate a complete admin panel. Existing data appears instantly — no migration, no duplication, no schema re-definition needed.
Is Rebase open-source?
Yes. The entire framework is free and MIT-licensed — the schema editor, data import/export, user management, generated APIs, typed SDK, and every feature ships at no cost, fully self-hosted. Optional paid plans add enterprise support, SSO/SAML, and SLAs; see pricing.
What's the tech stack?
The admin panel is a React 19 SPA built with TypeScript and Tailwind CSS. The backend is a lightweight Node.js service that connects directly to your PostgreSQL database. No SSR, no monolithic framework.
Do you support SSO or enterprise auth?
Yes. SSO, SAML, and advanced enterprise authentication are supported. Enterprise plans with dedicated support and SLAs are available — reach out to talk through your requirements.
Can I embed Rebase inside my existing React app?
Yes. Rebase is distributed as npm packages. You can mount the entire admin panel inside your existing React application, or deploy it as a standalone SPA. It's designed to be embeddable.
Stop writing glue code.
Define your schema. Get your platform.
Open-source, self-hosted, no per-seat pricing.


















