We build softwarethat earns its keep.

A product engineering studio. For over a decade we’ve built and shipped our own products — like FireCMS and Rebase — and we bring that same depth to yours.

Start a project See our work

Teams shipping products on software we wrote

Everything we build does the work for you.

One habit, in our own products and in client work alike: take the job somebody is doing by hand and make the software do it instead — properly, in production, for years.

RebaseA Postgres database you already ownA complete backend, with the access rules enforced by Postgres itself FireCMSA Firebase collectionAn admin panel your non-technical team can actually use DatakiA question typed in plain EnglishA real dashboard, with the SQL it wrote to get there Unbrand.myAny website addressA full brand book — colour ramps, contrast-checked pairings, type and spacing tokens SustenTalentA weekday scrape of public job postingsA live list of the employers hiring right now, enriched and queued, with the next step already worked out

None of that is a demo. Every row above is a product running in production right now, and the link takes you straight to it.

Automate something of yours

We don’t hand it over and disappear.

Most agencies ship a v1 and move on. We have never had that luxury — we build our own products too, and we are still running them.

FireCMS has been in production since 2020. Every schema we got wrong, every migration we had to ship without breaking thousands of live installs, every issue answered in public at midnight: we paid for those lessons on our own time.

It changes the questions you ask. Not “can we build this?” — almost anyone can build it — but “who is going to be maintaining this in four years, and will they curse us?”

That is what you are actually hiring. Not capacity. Judgement about the decisions that get expensive later.

Every number on this page links to where you can check it.

6 yrsFireCMS in production, merged into every week since 2020github.com/firecmsco/firecms 22kinstalls a month across our published npm packagesnpmjs.com/org/firecms 23+German and Swiss health insurers reimburse a product we builtmedicalmotion.com 12kinstalls a month of Neat, the gradient engine behind this pagenpmjs.com/package/@firecms/neat 3.7kcommits in public from one of us, on FireCMS alonegithub.com/fgatti675 6products of our own, all of them still runningsee the work below

Products in production. Not promises in a deck.

You can read about how we work, or you can go and use what we built. Everything below is live right now.

Based on your unique pain profile

AI-supported physiotherapy

Meditation and breathing exercises

Your Health Cockpit

medicalmotion

Client product · Digital health · medicalmotion.com

AI-guided pain therapy that doctors prescribe and insurers pay for.

We’ve built the technology behind medicalmotion since its first web version — the patient app, the therapist tooling, the personalisation engine, and the data platform behind their Pain Lab research. Medical data, German healthcare regulation, published clinical outcomes. The kind of product where a wrong architectural call isn’t a sprint you can redo.

23+insurers reimburse it

5+published efficacy studies

2019first version we shipped

ReactNodeGoogle CloudHealth data

Read the case study Visit medicalmotion

FireCMS

Our product · Open source · Since 2020 · firecms.co

The admin panel thousands of Firebase teams run their back office on.

It started as the internal tool we were tired of rebuilding for every client. Six years later it’s an open-source framework with a hosted cloud on top, used by product teams from health tech to logistics — and we’ve maintained every breaking change, written every docs page and answered every issue ourselves.

1.3kstars on GitHub

9knpm installs a month

220+forks

TypeScriptReactFirebase

Visit FireCMS

Rebase

Our product · Shipping now · rebase.pro

Point it at the Postgres you already own, and get a backend.

REST, auth, storage, realtime and a generated admin panel — with every access rule enforced by Postgres row-level security rather than middleware you have to trust. Built for teams who’d rather not hand production data to somebody else’s managed instance. Open source, self-hosted, European by design.

Opensource, MIT

Selfhosted, your infra

RLSenforced by Postgres

PostgresTypeScriptREST + GraphQLRealtime

Visit Rebase

SustenTalent

Client product · Job board · Spain and Latin America · sustentalent.com

A job board that fills its own pipeline.

A marketplace for sustainability and ESG roles, with the recruiting operation that works it built into the same product. A weekday scrape reads real vacancies down the employer axis rather than the posting axis, so the review queue doubles as a live list of companies hiring right now. An enrichment pipeline fills in the company behind each posting, the shared mailbox syncs itself, and the admin derives the next step for every prospect instead of asking anyone to keep a status column up to date.

Dailyvacancy scrape feeding the prospect list

RLSaccess enforced by Postgres, not app code

1 repopublic site, backend and admin panel

AstroReactRebasePostgresCloud Run

Read the case study Visit SustenTalent

Also built and running

Dataki

dataki.ai

Connect a database, ask a question in plain English, get a real dashboard — SQL included. BigQuery, Postgres, MySQL, Sheets.

Unbrand.my

unbrand.my

Point it at any website and it generates a brand book: colour ramps, contrast-checked pairings, type scale, spacing tokens. With an API.

Neat

neat.firecms.co

A WebGL gradient engine and editor — and the background of the page you are reading. 12k installs a month.

Dadaki

dadaki.com

A complete vector design tool that runs entirely in the browser. No install, no server round-trip, no plugin.

Plus a decade of consulting for product teams across Europe — from the first architecture call to the rescue mission six months after launch.

Four ways in. All of them scoped.

Every engagement starts with a fixed scope, a milestone plan and a price — not a discovery phase that bills for three months.

Automation and AI that survives production

The spreadsheet that gets re-keyed every Monday, the report somebody assembles from four dashboards, the approval that lives in an inbox. We find the ones worth automating and build them so they keep running without a babysitter — LLM features and agents included, with evaluation, cost control and a defined fallback for the day the model is confidently wrong.

Typically 3–10 weeks

Build the product

Zero to production, or the rewrite that finally scales. Design, frontend, backend and infrastructure owned by one team, so nothing falls between vendors — including the regulated kind, where the data is medical and the architecture has to survive scrutiny. We have been doing exactly that in German healthcare since 2019.

Typically 3–6 months

Data platform, Postgres and admin tooling

Schema design, painful migrations, row-level security, and getting off a managed backend you have outgrown without a weekend of downtime. Plus FireCMS and Rebase implementation from the people who wrote the frameworks.

Typically 1–8 weeks

Architecture review

Two weeks, a senior read on your stack, and a written plan your own team can act on. The cheapest way to find out whether you need us at all.

Fixed price, 2 weeks

Not sure which one you need? Neither are most people.

Tell us what’s stuck

Senior, transparent, weekly.

You always know what is being built, why, and what it costs.

Week one

A working session, not a questionnaire. You leave with a written scope, a milestone plan and a price that does not move.

Prototype early

Something clickable in your browser within weeks. We would much rather find out an idea is wrong in week two than in month four.

Ship every week

A live staging URL from day one and a demo every Friday, so nothing about the state of the work is a surprise at the end.

Hand over, or stay

Your repo, your infrastructure, your accounts, documented. We leave cleanly — or stay on as the team that keeps it alive.

Everything we know, in public.

Thousands of developers install our tools every month, and every decision we have made is sitting in a public commit history — along with the ones we had to walk back.

Six years of answering issues in the open is six years of mistakes we will not repeat inside your codebase.

Explore our GitHub

FireCMS

firecmsco/firecms

The headless CMS and admin panel for Firebase. Started in 2020, still merged into every week.

1.3k stars · 220 forks · TypeScriptCMSReactFirebase

Rebase

rebase.pro

REST, auth, storage, realtime and an admin panel generated from a Postgres schema you already own.

Open source · Self-hosted · PostgresPostgresSDKRealtime

Neat

@firecms/neat

The WebGL gradient engine rendering the background of this page. Three.js under the hood, one npm install on top.

12k installs a month · Three.jsWebGLShadersThree.js

Who you will be working with.

Three engineers who have been building things together for years.

Francesco Gatti

Engineering · FireCMS

Creator and maintainer of FireCMS, co-author of Rebase. Nearly four thousand commits of it in public, which is a slightly uncomfortable but very honest CV.

Mattia Lorenzutti

Product & engineering · medicalmotion

Co-founded Camberi and has led the technology behind medicalmotion since its first version — the patient app, the clinical tooling and the data platform underneath.

Marian Moldovan

Engineering · Rebase

Co-author of Rebase, the Postgres backend we build in the open, and a contributor to FireCMS. Backend and infrastructure — which is where most products actually break.

And a short list of specialists

For design, ML or mobile we bring in people we have worked with for years — by name, on the projects that need them.

Tell us what’s stuck.

Most of our work comes from people who already use something we made. The rest starts with an email — two paragraphs about your product and where it is blocked is plenty.

hello@camberi.com

Book a 30-minute call

We read everything and reply within one business day.

What happens next

01You write two paragraphs: what you are building, and where it is stuck.
02We come back with our first questions — or with a straight no, if this is not work for us.
03A 30-minute call about the product, the constraints and the deadline.
04A written scope: the milestones, and a price that does not move.

Working across European time zones