For SaaS & product teams

Give every client their own AI assistant, isolated by design.

Run Oaura as the AI layer inside your product. Each of your clients gets its own knowledge base, workflows and data, from one account you control. No per-client infrastructure to build.

How it's built

One platform. A walled-off space for every client.

Your product talks to Oaura once. Behind it, each client gets its own knowledge base, workflows and data — and nothing crosses between them.

Your SaaS product
app.yourproduct.com
Oauraone account · shared runtime · your LLM keys
Client A
Isolated
Knowledge base
Acme help center
Workflows & tools
Acme CRM · n8n
Data
Acme conversations & users
Client B
Isolated
Knowledge base
Globex product docs
Workflows & tools
Zendesk · webhook
Data
Globex conversations & users
Client C
Isolated
Knowledge base
Initech policies
Workflows & tools
ERP · MCP tools
Data
Initech conversations & users
Dashed walls: nothing is shared between client spaces — not documents, not tools, not conversations.
Every request

Answers come only from the client who asked.

Your app tells Oaura who is signed in. The question is answered from that client's space — the others are never searched.

A Client B user asks
“How do I export my invoices?” inside your app.
Identified as Client B
Your app passes the signed-in user and their organization.
Client B's space only
Searches Globex product docs; calls Zendesk · webhook.
Answer with sources
Cited from Client B's own documents.
Client A: not searched, not called Client C: not searched, not called
Your clients see

Their brand. Their answers.

Give a client its own agent for its own name and colours, or its own environment for layout, theme and starter questions. Remove the Oaura badge on Business.

A
Acme Assistant
What's the refund window?
Acme refunds annual plans within 30 days of purchase.
Acme billing policy
Ask Acme…
G
Globex Assistant
What's the refund window?
Globex offers refunds within 14 days for monthly plans.
Globex terms of service
Ask Globex…
Same question, one Oaura account — each client sees its own brand and gets its own answer.
What it handles

One agent, several jobs.

An environment per client

One agent, one environment per client: its own prompt, starter questions, widget look and tools. Business plan.

Separate knowledge bases

Each client answers only from its own documents. Assign a knowledge base per environment, or tag it with your client ID through the API.

Per-client workflows

Connect each client's n8n workflows, webhooks and MCP tools only where that client needs them.

Separate data per client

Conversations and end users are kept per client. Give a client its own agent when you need a hard wall between them.

Knows which client is asking

Pass your signed-in user and their organization from your app. Your tools receive the tenant ID with every call.

API-first

Create client knowledge bases, upload documents and run conversations from your backend with the REST API, filtered by client ID.

How it works

Getting set up.

  • 1Create an agent for your product and add an environment (or a dedicated agent) for each client.
  • 2Load each client's documents into their own knowledge base — from the dashboard or with the REST API and a client ID.
  • 3Connect the workflows and tools each client needs — nothing is shared unless you share it.
  • 4Embed the widget in your app and pass the signed-in user, so every answer comes from the right client's data.
  • 5Tune each client's prompts, tools and knowledge from the dashboard, without redeploying your app.

Ready to set up SaaS & product teams?

Five-minute setup. Bring your own LLM. No credit card.