Pricing
Start free. Pay when it’s real.
Three tiers, and the numbers below are exactly what the platform enforces in code: real limits, flat pricing, and a bill that stays the same every month.
One project, real API, enough room to prove the idea works.
No card required. Idle projects pause after 7 days.
Request access →- 1 project, 3 tenants
- 100 MB storage
- 120 requests / minute · 100K per month
- 7-day audit log retention
- Schema, relations, generated REST API
- Rules: create, update, delete triggers
- Formulas, scheduled rules, many-to-many (Pro and up)
The whole platform, for the products you actually ship.
Billed monthly. Up to 5 projects.
Request access →- 5 projects, 50 tenants each
- 5 GB storage
- More database resources
- 1,200 requests / minute · 5M per month
- 30-day audit log retention
- Computed and stored calculated fields
- Scheduled rules, rule chaining, branches
- Multi-step webhooks, nested writes, related records
For regulated industries and tenants who ask hard questions.
Limits and terms configured to your requirements.
Contact sales →- Dedicated database per tenant
- Projects, tenants, storage and rates tailored to you
- 365-day audit log retention
- Move a tenant to its own database with your code untouched
- Everything in Pro
Compare every tier
What’s in each plan.
| Feature | Free | Pro | Enterprise |
|---|---|---|---|
| Limits | |||
| Projects | 1 | 5 | Tailored to you |
| Tenants per project | 3 | 50 | Tailored to you |
| Storage | 100 MB | 5 GB | Tailored to you |
| Requests per minute | 120 | 1,200 | Tailored to you |
| Requests per billing period | 100K | 5M | Tailored to you |
| Audit log retention | 7 days | 30 days | 365 days |
| Idle projects paused after 7 days | ✓ | — | — |
| Data model | |||
| Entities, fields, relations | ✓ | ✓ | ✓ |
| Schema versioning and integrity checks | ✓ | ✓ | ✓ |
| Per-tenant custom fields | ✓ | ✓ | ✓ |
| Computed fields | — | ✓ | ✓ |
| Stored calculated fields | — | ✓ | ✓ |
| Many-to-many relations | — | ✓ | ✓ |
| Cascade / set-null on delete | — | ✓ | ✓ |
| API | |||
| Generated REST API per entity | ✓ | ✓ | ✓ |
| Filtering, sorting, pagination | ✓ | ✓ | ✓ |
| OpenAPI spec per project | ✓ | ✓ | ✓ |
| Related records in one call (?include=) | — | ✓ | ✓ |
| Nested writes across related entities | — | ✓ | ✓ |
| Rules | |||
| Before / after create, update, delete | ✓ | ✓ | ✓ |
| Conditions, lookups, blocking | ✓ | ✓ | ✓ |
| Single-step webhooks | ✓ | ✓ | ✓ |
| Scheduled (cron) rules | — | ✓ | ✓ |
| Rule chaining | — | ✓ | ✓ |
| True / false branches | — | ✓ | ✓ |
| Multi-step webhook pipelines | — | ✓ | ✓ |
| Isolation | |||
| Tenant scoping enforced on every request | ✓ | ✓ | ✓ |
| Separate data space per project | ✓ | ✓ | ✓ |
| More database resources | — | ✓ | ✓ |
| Dedicated database per tenant | — | — | ✓ |
Questions
Before you ask.
What counts as a request?
Every authenticated call to your project’s API, reads and writes both. Calls rejected because the key is missing or invalid are not counted, and neither are calls that get throttled.
What happens when a project hits its request quota?
The API returns 429 REQUEST_QUOTA_EXCEEDED for the rest of the billing period, and the response tells you when the period resets. Quotas are per project, so one busy project does not spend another’s allowance. Your bill stays the same every month.
And when storage runs out?
Writes return 507 STORAGE_QUOTA_EXCEEDED while reads keep working, so your product stays live in read-only rather than going dark. Clearing space or moving up a tier lifts it on the next nightly measurement.
What exactly is a tenant?
One of your customers. If you are building software for clinics, each clinic is a tenant. Their staff and end users are not tenants and are not counted, and Fluidlee leaves them entirely with you.
Why do Free projects pause?
A Free project with no API activity for 7 days is paused, and its API answers 503 PROJECT_PAUSED until the project is reactivated. Everything is kept: your schema, rules and data stay exactly as they were. It keeps abandoned projects from occupying shared capacity. Pro and Enterprise projects always stay live.
Can I move between tiers later?
Yes, in both directions. Moving up raises limits immediately. Moving an Enterprise tenant onto its own dedicated database copies its data across and re-routes it, and your code stays the same, only the connection behind it moves.
Do you store our end users’ personal data?
No. Fluidlee knows about you, your projects, and your tenants. Your end users are opaque to us. You may pass an anonymous actor id so the audit log can record who did what, and that is all we keep.
Not sure which tier fits?
Tell us what you’re building and roughly how many tenants you expect. We’ll point you at the right starting point.