> For the complete documentation index, see [llms.txt](https://oodlz-ai-studio.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oodlz-ai-studio.gitbook.io/docs/architecture-and-stack/multi-tenant-isolation.md).

# Multi-Tenant Isolation

Every brand signs up for their own cloud accounts — n8n, Airtable, Pinecone, fal.ai, Zernio, and their CMS. Nothing is shared.

> **Not a tenant in someone else's platform — the owner of every account in the stack.**

Most "multi-tenant" SaaS runs every customer inside one provider's cloud — shared workflow engine, shared database, shared vector store — partitioned by tenant ID. The Oodlz architecture is the opposite: every brand signs up for their own cloud accounts. Nothing is pooled, nothing is partitioned, nothing is shared.

## How It Works

Every brand owns the full set of cloud accounts the platform runs on:

| Account         | What it does                                                                                                      |
| --------------- | ----------------------------------------------------------------------------------------------------------------- |
| n8n cloud       | The brand's workflow engine. Every producer runs on this instance.                                                |
| Airtable        | The brand's workspace base. Brand profile, content pipeline, approval queues, and performance data all live here. |
| Pinecone        | The brand's vector index. Catalogue, FAQ, and instructional content are isolated to this index.                   |
| fal.ai          | The brand's image rendering account. Generation usage and history are scoped to the brand.                        |
| Zernio          | The brand's social scheduling account. Connected social channels and dispatch logs live here.                     |
| The brand's CMS | The brand's publishing site. Articles draft and publish here.                                                     |

There is no Oodlz cloud in the middle. No shared infrastructure, no row-level filtering, no cross-brand vector queries. A brand's data physically cannot reach another brand's pipeline because the pipelines run on different accounts on different services.

![Multi-tenant isolation — typical SaaS partitions every customer inside one provider's cloud; with Oodlz AI Studio, every cloud account is the brand's own — n8n, Airtable, Pinecone, fal.ai, Zernio, and their CMS](https://2935174940-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9WhvO5Y38RJO9oNIdz9G%2Fuploads%2Fgit-blob-b8a970405193783d50b95812a054c2ebf0b6825f%2Fdiagram-multi-tenant-isolation.svg?alt=media)

## What You Get

* Full physical isolation per brand — every workflow, every dataset, every vector lives in the brand's own accounts.
* No cross-brand contamination possible — the architecture, not just access controls, prevents it.
* Independent capacity per brand — one brand's high-volume month doesn't compete with another brand's resources.
* Brand-specific configuration freely — settings, credentials, prompt customisations are scoped to one brand without affecting others.
* Independent failure domains — an incident on one brand's stack cannot cascade to another's.
* Account portability — if a brand ever leaves, the accounts and data stay with them. Nothing to extract from a shared provider.