Where MITHUNAI runs and what it connects to

MITHUNAI is provided as a hosted service: the console is at https://app.mithunai.com/, the API at https://app.mithunai.com/mithunai/api/v1, and the widget script at https://app.mithunai.com/widget/mithunai-widget.js. There is no public installation package or self-service install. If you need MITHUNAI in your own environment, talk to your MITHUNAI contact before planning around it, and see the limits below.

What a deployment consists of

Component	Role
API	Serves the console, the HTTP API, the widget endpoints and the MCP server
Ingestion workers	Fetch, extract, redact, chunk and embed your content in the background
PostgreSQL	Stores knowledge, conversations, settings, invitations, saved connections and usage counts; `pgvector` and full-text indexes serve retrieval
Redis	Rate limiting, the background job queue and short-lived password-reset links, and cached question embeddings for grouping

What it calls outside itself

Your content leaves a deployment only in calls to:

The model providers it is configured with, to embed content, write answers and compare questions when grouping them by meaning: Anthropic, OpenAI or Google, or an endpoint the operator points one of those interfaces at, such as the Model Gateway. The relevant passages of your content are sent with each question. See Models and providers.
The sources you connect: the websites, sitemaps, OpenAPI schemas, Zendesk help centres and Discourse forums you add, each at the address you gave, and the GitHub API for repository sources. A Confluence source calls only the Confluence Cloud site its connection was saved with, and a Notion source only Notion’s API, each with your saved token. A custom answers source and an uploaded file call nothing.
The email provider, when the operator has set one up: the recipient’s address and the message of each invitation and password-reset email. No content from your sources is sent this way.

A deployment cannot answer or ingest without a model provider: one that offers a chat model, and one that offers an embedding model. If you need those to be models you host yourself, or a deployment with no outbound calls at all, raise it with your MITHUNAI contact before planning around it.

Settings the operator controls

Some behaviour is set for the whole deployment by whoever operates it, not from the console.

Setting	Default	Where it is described
Model providers and their models	None until configured	Models and providers
Scheduled re-sync of sources	Off	Scheduled re-sync
Upload size limit	1 MiB per file	File uploads
Where the widget may load	A website must be allowed by the operator and by the embed. The operator can let each embed’s own list decide alone	Allowed origins
Accounts and organisations	Organisations are created by the operator; people join by invitation once email is set up	Accounts and roles
Email, for invitations and password reset	Off: nothing is sent, and both answer that email is not set up	Invitations
Monthly answer allowance	One default for the deployment, which the operator can change for each organisation or remove	Usage and limits
Encrypted storage for saved connections	Needs a key the operator sets; without it, saving a connection answers that it is not available	Saved connections

Health checks

Endpoint	Use
`GET /health`	Liveness. Takes no credential and does no work
`GET /ready`	Readiness. `200` when every dependency it checks answers, `503` otherwise, with one word per dependency

Not offered today

A published service-level agreement or uptime commitment.
A choice of data region.
Customer-managed encryption keys.
Certifications or attestations such as SOC 2 or ISO 27001. See Compliance.

If any of these is a requirement, raise it with your MITHUNAI contact before you commit.

Account and sign-in

Members

Organisation

Usage

Security, compliance and deployment

Where MITHUNAI runs and what it connects to

What a deployment consists of

What it calls outside itself

Settings the operator controls

Health checks

Not offered today

​What a deployment consists of

​What it calls outside itself

​Settings the operator controls

​Health checks

​Not offered today

What a deployment consists of

What it calls outside itself

Settings the operator controls

Health checks

Not offered today