Skip to content
All case studiesPlatform

BurgerBase — a self-hosted backend for Base44 apps

A self-hosted Node.js / TypeScript backend that replaces Supabase for React apps generated with Base44 — JWT auth, a dynamic REST API, sandboxed Deno functions and an automated deploy CLI.

Node.jsTypeScriptDenoJWTRESTFileMakerDocker
Multi-client
In production (FMQC, Map Assistance…)
0
Vendor lock-in (replaces Supabase)
1 CLI
Automated deploys

The challenge

Base44 generates polished React front-ends fast, but every project came wired to a hosted backend (Supabase). For clients who need their data on their own infrastructure — on-premise, behind their firewall, alongside a FileMaker database — that hosted dependency was a non-starter.

Approach

BurgerBase is a drop-in backend that speaks the same contract the generated front-ends expect, but runs wherever the client needs it:

  • Auth — JWT-based authentication and session handling.
  • Dynamic REST API — collections and endpoints defined from configuration, so a new app doesn’t need new backend code.
  • Sandboxed functions — custom server logic runs as Deno functions in a sandbox, isolated from the host.
  • Integrations — first-class hooks for FileMaker, SMTP, and LLM providers (Anthropic, OpenAI, Ollama) so apps can read business data and call models without extra plumbing.
  • Deploy CLI — one command provisions and updates an instance on Windows Server or Linux.

Result

BurgerBase now backs several production apps for different clients (including FMQC and the Map Assistance / Magnus Poirier project), on a mix of Windows Server and Linux hosts — each with the client’s data staying on the client’s infrastructure.

Add deployment counts, a short architecture diagram and a client quote via the admin panel.

Want an outcome like this?

In production for multiple clients on both Windows Server and Linux, with FileMaker, SMTP and LLM (Anthropic / OpenAI / Ollama) integration built in.

Book a call
Next case study →

Doctoral Student Management Application