---
title: "Multi-tenant architecture"
description: "Serving many customers from one system without letting their data meet."
url: https://lidvizion.ai/resources/basics/multi-tenant-architecture/
site: Lid Vizion
index: https://lidvizion.ai/llms.txt
---

[Basics](https://lidvizion.ai/resources/) Architecture

# Multi-tenant architecture

Serving many customers from one system without letting their data meet.

## What it means

A multi-tenant system serves many customers — tenants — from shared infrastructure. Each tenant sees only its own data and settings, while the code, servers and upgrades are shared.

## Ways to isolate tenants

There are three common patterns, from most shared to most separate:

- Shared tables, where every row carries a tenant identifier that every query must filter on.
- A separate schema or database per tenant inside a shared server.
- Fully separate deployments for tenants with strict requirements.

## Where AI makes it harder

AI features add new places data can leak: retrieval indexes, prompt logs, caches and fine-tuning sets. Each needs the same tenant boundary as the main database, and tests that prove one tenant cannot retrieve another tenant’s content.

Put it to work

## Build the missing piece

Custom tools and applications for the gaps that matter.

[How we do it](https://lidvizion.ai/services/custom-software/)

Keep reading

## More basics.

[All basics](https://lidvizion.ai/resources/)

- [Edge vs. cloud deployment](https://lidvizion.ai/resources/basics/edge-vs-cloud-deployment/): Where a model should run: next to the camera or sensor, or in a data centre.
- [Client vs. server: where code runs](https://lidvizion.ai/resources/basics/backend-client-vs-server/): What belongs in the browser or app, and what must stay on a server you control.
- [What is computer vision?](https://lidvizion.ai/resources/basics/what-is-computer-vision/): Software that turns images and video into structured information a system can act on.

Bring the messy version

## One workflow. A better way to run it.

Show us the tools, the handoffs, and the part that keeps slowing your team down.

[Let’s map your workflow](https://lidvizion.ai/contact/) · [Read our approach](https://lidvizion.ai/approach/)