Security & architecture
Isolation that enforces itself.
The safeguards below are built into the platform and enforced on every request, so they’re handled for you rather than something your application has to remember.
01 · Isolation
Every request belongs to exactly one tenant.
Isolation lives in the data layer, handled for you instead of in a WHERE clause
your code has to remember. A request scoped to one tenant only ever touches that tenant’s
data, even if your application code has a bug.
Separated by project
Each project keeps its own data space, apart from every other project, including your own others.
Scoped by tenant
Every row carries its tenant, and every query is confined to the tenant named on the request, enforced by the engine itself.
Dedicated when required
Tenants under strict contracts can move to a database of their own, with dedicated storage. Your code stays the same, only the connection behind it moves.
Secrets that stay secret
- Keys are hashed at rest. The plaintext is shown once at creation and kept only as a hash from then on.
- Multiple keys per project, each with its own name, for different environments or integrations.
- Revoke instantly, and permanently. Every key tracks when it was last used.
- The key belongs on your server, where every Fluidlee call is made.
A record of every change
- Every create, update and delete is logged with the actor, a timestamp, and a before/after diff.
- Searchable and filterable in the dashboard by entity, tenant, actor and date.
- Retention scales with your tier, up to 365 days on Enterprise.
- Records are soft-deleted: a delete sets a timestamp and hides the row, so your history stays intact.
Every write arrives clean
- Every write is validated against the schema: types, required fields, and formats.
- Foreign keys are checked against the same tenant, so every reference stays within its tenant.
- Read-only, computed and system fields are stripped from incoming requests, so the platform stays in control of the fields it manages.
- A schema change that would break a live rule is caught up front, long before production.
Guardrails on every project
- Rate limits per minute and request quotas per billing period, both per project.
- Storage quotas that ease a full project into read-only, keeping it steady and predictable.
- Over-limit responses are clear and consistent: a stable status code and a reset time, so billing stays flat.
06 · Your end users
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’s all we ever keep about them. Their names, emails and personal data stay entirely with you.
Have specific requirements?
If your industry comes with obligations around data residency, retention, or isolation, the Enterprise tier is where we work through them with you. Talk to us about your compliance requirements →
Want the architecture walkthrough?
We’re happy to go deep on isolation, key handling and audit with your security team.