Bodhi LogoBodhi
DocsGitHubDiscord

Home

IntroductionInstallation
Concepts
OverviewDeployment ModesModels, Aliases, and FilesAPI CompatibilityAuth and RolesMCP Overview
Features
ChatModelsSettingsMCPsAuth
Deployment
Deployment OverviewDesktop (Tauri)DockerReverse Proxy
Developer
Getting StartedBuilding Third-Party AppsBodhi JS SDKBrowser ExtensionApp Access RequestsOpenAPI Reference
API Compatibility
OverviewOpenAI Chat CompletionsOpenAI ResponsesOpenAI EmbeddingsAnthropic MessagesGeminiOllama (deprecated)MCP ProxyError Format
Advanced
ArchitectureSecurity ModelInference StackPerformance TuningObservability
Reference
Environment VariablesSettings PrecedenceRoles and ScopesError CodesGlossary
Support
FAQTroubleshootingWhat's New

In This Section

  • Overview
  • Deployment Modes
  • Models, Aliases, and Files
  • API Compatibility
  • Auth and Roles
  • MCP Overview

Home

Concepts

Overview

The mental model behind Bodhi App: one server, many compatibility layers, local + remote inference, MCP tools, role-based auth

Deployment Modes

Tauri desktop vs Docker single-tenant — the two ways to run Bodhi App, and how to pick

Models, Aliases, and Files

The three things "model" can mean in Bodhi — file vs alias vs API model — and how they relate

API Compatibility

Why Bodhi exposes OpenAI, Anthropic, Gemini, and Ollama wire formats simultaneously — and what that means for your client

Auth and Roles

OAuth2 PKCE, four roles (User / PowerUser / Manager / Admin), session cookies vs API tokens, and how scopes work

MCP Overview

Model Context Protocol in Bodhi: per-user instances, three auth methods, the playground, and the MCP proxy for external apps