Vol. XI · Functory Quarterly№ 001 · Edition 2026
I
Components

Multi-Tenancy.

Many customers, one deployment, real isolation

One deployment serves many end-customers as separate tenants. Each gets its own subdomain, its own users, its own data, and its own entity catalog, so two tenants of the same deployment can run genuinely different applications. Isolation is structural rather than advisory: a query that omits the tenant addresses a partition that does not exist, so there is no filter to forget.

II
Key features

Everything you need.

6 capabilities, all production-ready.

  1. 01

    Per-tenant subdomains, users, and data partitions

  2. 02

    Per-tenant entity catalogs layered on a shared default set

  3. 03

    Isolation carried through search, SQL, cache, and the event stream

  4. 04

    Tenant-scoped identity, so one email is two people in two tenants

  5. 05

    Suspension as a distinct state from an unknown tenant

  6. 06

    Tenant registration and switching from the admin console

III
Integrations

Works with everything.

Multi-Tenancy integrates seamlessly with other Functory products and your existing tools.

Event-Driven ArchitectureTask SchedulingNotificationsREST & GraphQL APIsYour AWS Account

Coda

Ready to ship?

We build with Multi-Tenancy, so you do not have to.

Tell us what you are building, or browse the rest of the catalogue.