A REST API from your schema
Sketch your entities in the dashboard. The API is there before you refresh the page. Validation, relations and an OpenAPI spec come with it.
Your backend, handled
Define your data model, and Fluidlee gives you the whole backend around it: schema, REST API, tenants, rules and audit. Your backend calls it with one API key, and your team stays free for the part of the product only you can build.
GET /patient POST /invoice entity = invoicecurrency = "USD""Manual review required"The pitch
If you’re building a software product, you already know the foundation it stands on: Tenants. Audit. Permissions. A way for non-engineers to shape the data model. Webhooks that fire the moment something changes.
That’s the part we love to run for you, so you can pour your time into the product only you can build.
01 · What you get
Six essentials, delivered as one API and one dashboard, so your energy goes straight to the product your customers came for.
Sketch your entities in the dashboard. The API is there before you refresh the page. Validation, relations and an OpenAPI spec come with it.
Tenants are isolated at the data layer. Every read and write is scoped to one tenant, and every change lands in an audit trail that’s ready from day one.
Computed fields, before and after hooks, scheduled jobs, webhooks: the logic that shifts as your business does, now something your team can adjust in a few clicks.
Fluidlee is a server-to-server API. Your backend holds the API key, maps each logged-in user to a tenant, and calls us on their behalf. Your auth stays yours, and we work quietly behind the scenes.
Most tenants happily share infrastructure. When a contract calls for more, move that tenant to its own database, and your code stays exactly the same.
A real UI for editing schemas, drawing rules, testing requests and reading audit logs, friendly enough that most days your whole team runs it, not just your engineers.
02 · See it work
Your backend authenticates against Fluidlee, names the tenant, and reads or writes, like any other REST API.
curl https://api.fluidlee.com/invoice \ -H "Authorization: Bearer flk_live_a8f3..." \ -H "X-Tenant-ID: 550e8400-e29b-41d4-a716-446655440000" \ -H "X-Actor-ID: usr_2f10" \ -H "Content-Type: application/json" \ -d '{ "patient_id": "550e8400-...", "amount": 1840.00, "status": "pending" }' # before_create rules run · audit entry written { "data": { "id": "8a91c4b2-...", "created_at": "2026-07-24T14:22:11Z" } }
03 · How it works
Entities, fields, relations, drawn on a canvas. Reshape it whenever the business evolves.
patient · invoice · clinician The API exists the moment the schema does. Tenants and isolation are already wired up.
flk_live_a8f3… Scoped to whichever tenant the logged-in user belongs to. Your frontend talks to your backend, like always.
Authorization: Bearer … 04 · Pricing
The limits below are exactly what the platform enforces: clear, honest, and the same at the end of the month as the day you signed up.
We’re welcoming a few teams in at a time. Send a few sentences about the product and what you’d love your backend to handle.