Skip to content
giron.ai
← All writing

Multi-tenant from day one: the decision that saved me

It is the one thing you cannot retrofit without rewriting the product.

Published
8 May 2026draft
Category
SaaS and architecture
Reading
8 min

This piece is published as an outline: the statement and the structure are settled, the full text is coming.

The cost of postponing

Adding isolation to a schema that assumed a single customer is not a migration: it is a rewrite with customers on top of it.

Isolation in the database, not the code

Row level security: the query you forget to filter cannot return another tenant’s rows, because the engine will not let it.

When one tenant grows ten times faster

Partitioning, per-tenant indexes and the noisy neighbour.

What eight years taught

What I would do the same way again, and what I would not.

Write to me

If you are thinking about building something with AI and want to talk it through with someone who has put it into production, write to me. I answer myself.

hola@giron.ai