You build the backend and the back office on a Postgres the client owns, under a licence nobody can revoke. When the engagement ends, they keep the database and you keep the code — and neither of you is renting the thing in between.
Every client project needs the same layer: REST over their tables, a typed client, sessions, file uploads, permissions that hold. It is the least differentiated work on the invoice and the easiest to get subtly wrong.
Rebase generates it from the client's own schema, with the access rules compiled into Postgres row-level security rather than into middleware your successor has to remember. The panel comes off the same definition, so the operator team gets a back office without a second sprint for it.
Controllers, serializers, validation and the OpenAPI document, generated from the collection definition and regenerated when it changes.
Written once beside the collection, compiled into Postgres policies. A table with no rule is refused rather than served, so a forgotten endpoint cannot leak it.
Tables, forms, media, relations and roles render from the same definition, and your own React components go in wherever the generated field is not enough.
A custom field, a custom preview, a whole custom view or an entity action — each is a React component referenced from the collection, not a fork of the panel.
Branding, theme and copy are configuration, so the same codebase can be handed to two clients that look nothing alike.
Written once for one client, reused on the next without asking anyone's permission.
Build custom fields and views once, reuse across client projects.
Logo, palette and copy are config values, not a patched build.
Per collection, per field, per role — and enforced by Postgres, not by the panel.
A published container and a Postgres connection string. Docker, Fly, Railway, Hetzner or their own metal.
Self-host on the client's own infrastructure, or run it on Rebase Cloud — in private beta today.
No template language, no proprietary builder. The people you already employ can read it.
Built on it
Each of these runs on a Postgres database its owner controls. Built by the Rebase team.
06·Built for real products
From marketplaces to retail loyalty, public data and internal tools — seven very different products, the same definition underneath.
Vector Design Tool · Built by the Rebase team
Our own product: a fast, in-browser vector editor with cloud sync. Dadaki runs on a completely standard Rebase backend — the same auth, storage, and generated APIs every project gets.
dadaki.com
Digital Pain Therapy
A certified digital medical device delivering AI-personalized pain therapy. Rebase runs the entire backend — patient records, therapy plans, the exercise content library, and the clinical dashboards on top of them.
medicalmotion.com
Marketplace & Job Portal
A two-sided marketplace connecting sustainability professionals with green companies. Rebase powers both sides of the market: role-based auth, typed matching APIs, and the moderation back office.
sustentalent.com
Public data · Built by the Rebase team
A public reading of Spanish government spending, from €725bn down to a single budget line. There is no database in the read path: a cron recompiles the official figures each month, storage serves them as JSON, and the page itself makes zero API calls.
presupuestos.rebase.website
AI sales agent · Built by the Rebase team
An outbound agent that reads your site, plans audiences, then finds real companies and the people at them — each one verified against its own website. Crons, functions and the review board are stock Rebase. It drafts; the schema has no state in which it sends.
prospector.rebase.website
Retail loyalty
The loyalty programme behind an apparel brand. Orders from Odoo POS and Shopify land in Postgres, a tier engine recomputes points and discounts, and the Apple and Google Wallet passes customers scan at the till are issued from the same schema.
unfeignedgear.comInternal tool · CRM and workflow automation
A CRM the team can rebuild without a deploy: pipelines, tags, tasks and an automation canvas whose triggers, branches and actions are all rows in Postgres. Twenty-three collections generated the entire back office — no admin screens were written.
Internal tool — no public site
01/07
Scaffold against the client's own Postgres. They keep the database, you keep the code, nobody rents either.
