Twin Browser
Get an API key
PlatformOverviewHow it worksAll toolsREST APIMCP serverIntegrationsDocs
CapabilitiesSemantic dispatch cacheDeterministic replayCross-tenant skill corpusToken-efficient DOMHuman-in-the-loopLive view & videoCredential vaultOverviewSolutions
SolutionsAll use casesAI agentsRPA replacementQA & test automationData extraction
ResourcesGuidesGlossaryBlogCompareFAQStatus
Pricing
Log in

Glossary · Identity & access

Multi-tenant isolation

The guarantee that one tenant’s runs, skills, sessions and secrets are unreachable from another — enforced in the database, not the application.

Start freeAll terms

What is multi-tenant isolation?

Multi-tenant isolation means every row is owned by a tenant and readable only through that tenant’s identity. Here the tenant is always derived from the authenticated API key and never read from a request body, and access is default-deny at the database level rather than filtered in application code.

Why it matters

Application-level filtering fails open — one forgotten WHERE clause is a cross-tenant leak. Default-deny at the row level fails closed: a query that forgets the tenant returns nothing instead of everything.

Related terms

See it in context

Back to the full glossary

Put your agent to work. Keep the decision.

Give your agent a real browser, authorize the accounts it may use, and keep control of every step. Repeated runs compile into skills that replay without a model.

Start freeSee pricing