BodhiApp
Self-hosted AI gateway for local GGUF models, cloud APIs, and MCP tool calling behind one authenticated endpoint.
Pick Bodhi App when you want local GGUF inference, cloud API proxying, and MCP tool calling behind one authenticated server instead of stitching three tools together. The OAuth2 PKCE + JWT stack with four-role RBAC is unusually complete for a self-hosted gateway, and the Anthropic OAuth path means you can route Claude traffic through it with a subscription rather than a metered key. If you don't want to run Docker, pull multi-GB weights, and own a reverse proxy, a managed gateway is the easier
Verified 2d ago · liveness 68/100 · cite: rightaichoice.com/tools/bodhiapp
- Developers building AI apps who need local inference and cloud API access behind one endpoint
- Teams deploying a self-hosted gateway with real multi-user auth and role-based access control
- Engineers connecting MCP servers and tool calling to both local and cloud models
- Organizations that need OAuth2 PKCE sign-in, access request approvals, and audit trails
- Users who want a fully managed cloud AI service with no infrastructure to run
- Non-technical users unwilling to run Docker or install a desktop app
- Teams without GPU or disk capacity for multi-gigabyte GGUF model files
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip Bodhi App if you want a vendor to run the gateway for you — there is no hosted option, so you deploy Docker or a desktop app, pull multi-GB GGUF weights, and own the reverse proxy and backups.
Bodhi App is free and open source, so the cost that matters is infrastructure, not licensing: GPU hardware or cloud GPU time, disk for multi-GB GGUF files, and engineering hours for Docker deployment, reverse-proxy TLS termination, and backups. Compare that against a managed gateway charging per token or per seat, where you trade cash for not running anything.
In short
BodhiApp — Self-hosted AI gateway for local GGUF models, cloud APIs, and MCP tool calling behind one authenticated endpoint. Best for Developers building AI apps who need local inference and cloud API access behind one endpoint, Teams deploying a self-hosted gateway with real multi-user auth and role-based access control, Engineers connecting MCP servers and tool calling to both local and cloud models. Free to use.
What's new in BodhiApp
Checked todayAcross the latest 2 updates: 1 feature update and 1 news mention.
Ollama compatibility layer marked deprecated; OpenAI, Anthropic, and Gemini formats remain supported
The Ollama chat and models endpoints are documented as deprecated, signalling a shift toward the OpenAI, Anthropic, and Gemini wire formats as Bodhi App's supported compatibility surfaces.
Anthropic OAuth support: use a Claude.ai or Anthropic Console subscription instead of an API key
Bodhi App can authenticate to Anthropic with an OAuth Bearer token drawn from a Claude.ai or Anthropic Console subscription, so you can route Anthropic traffic through the gateway without managing a per-token API key.
What people actually say about BodhiApp — is it worth it?
We ran a structured research pass across product reviews, community discussions, and post-purchase forum threads to surface the patterns vendors won't publish themselves. Below: the recurring strengths, the hidden costs people mention most, and the cohort that consistently regrets adopting this tool.
10 mentions across 2 sources (Hacker News, GitHub) · researched Jul 3, 2026.
Average across the 2 sources that answered — each source counts once, not each post.
- +Unified local and cloud models via OpenAI-compatible API.
- +Enterprise-grade OAuth2 + JWT authentication out of the box.
- +One-click GGUF model downloads with resume support.
- +Built-in chat UI with markdown and streaming.
- +Docker images optimized for multiple GPU backends.
- −Memory allocation errors on phi-3.5 and large models.
- −Homebrew installs wrong architecture on some Macs.
- −Missing llama-server-bindings in source code occasionally.
- −Windows build not yet available as of mid-2024.
- −No extension/plugin support like Jan AI.
- • No hidden costs—fully free and open-source.
- • Cloud API usage incurs provider fees (OpenAI, Anthropic) not covered by BodhiApp.
Viability Score
How well maintained and how widely used is BodhiApp? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: October 2026
How we score →Key Features
- Run local GGUF models via llama.cpp on your own hardware
- GPU acceleration across CUDA, ROCm, Vulkan, MUSA, Intel, and CANN
- 8-12x inference speedup with GPU acceleration over CPU inference
- Proxy OpenAI, Anthropic, and Gemini APIs through one authenticated endpoint
- Anthropic OAuth authentication using a Claude.ai or Anthropic Console subscription
- OpenAI Chat Completions, Responses, and Embeddings compatible endpoints
- Anthropic Messages API compatibility layer
- Gemini API compatibility layer
- Ollama chat and models endpoints (deprecated)
- MCP tool integration with per-user MCP instances and agentic mid-conversation tool calls
- MCP Playground for testing servers and individual tools
- Three MCP auth methods: Header, OAuth2 preregistered, OAuth2 Dynamic Client Registration
- Per-conversation MCP tool whitelists and admin-published MCP server catalog
- Built-in chat UI with markdown, live token streaming over Server-Sent Events, and thinking-model reasoning view
- Model aliases binding a GGUF file to 12+ inference parameters without restarts
About BodhiApp
Bodhi App is a self-hosted AI gateway that puts local GGUF inference and cloud API providers behind one authenticated server you run yourself. Local models execute through llama.cpp with GPU acceleration, and the vendor cites an 8-12x speedup with GPU acceleration over CPU-only inference. You pull weight files straight from HuggingFace with background downloads that track progress and auto-resume, then serve them through a built-in chat UI with markdown, model settings, thinking-model chain-of-thought, and real-time token streaming over Server-Sent Events. The gateway also proxies OpenAI, Anthropic, and Gemini traffic using your own credentials. Anthropic OAuth support lets you authenticate with a Bearer token drawn from a Claude.ai or Anthropic Console subscription instead of a metered API key. Existing client libraries connect without code changes because the server speaks OpenAI Chat Completions, Responses, and Embeddings plus Anthropic Messages and Gemini wire formats. The Ollama compatibility layer is now marked deprecated, with the vendor steering users toward the OpenAI, Anthropic, and Gemini surfaces. MCP integration lets models discover and invoke external tools mid-conversation. You get per-user MCP instances, three auth methods (Header, OAuth2 preregistered, OAuth2 Dynamic Client Registration), a playground for testing servers and individual tools, and per-conversation tool whitelists. Model aliases bind a GGUF file to 12+ inference parameters so you switch configurations without restarting. There is also a JS SDK with React hooks, an OpenAPI/Swagger UI, and scope-based API tokens hashed with SHA-256. For teams, Docker deployment ships OAuth2 PKCE + JWT auth, four roles (User, PowerUser, Manager, Admin), a self-service access request workflow with admin approval and audit trail, and app access consent controls. It suits developers who want inference and data on their own hardware and teams needing real multi-user auth rather than a single-user local
Behind the Verdict
Bodhi App's pitch is consolidation, and it's a fair one. Most teams running local models against agentic workloads end up gluing a llama.cpp server, an API proxy, and a separate MCP tool runner together with their own auth in front. Bodhi collapses that into one binary you operate, which removes a class of integration drift problems. If the multi-tool duct-tape setup has been nagging you, this is a direct replacement. The genuinely differentiated part isn't the model serving, it's the multi-user plumbing. Four roles, OAuth2 PKCE sign-in, self-service access requests with an admin approval gate and audit trail, session invalidation, and per-conversation tool whitelists — that's the layer single-user local runtimes skip entirely. We'd reach for it when more than a couple of people need to share inference hardware without sharing one API key. Watch the Ollama deprecation. If your existing scripts hit /api/chat or the Ollama models endpoint, plan a migration to the OpenAI, Anthropic, or Gemini formats now rather than later. The vendor keeps the endpoints but flags them, so this isn't an emergency — it's a direction of travel. The Anthropic OAuth route is worth a close look if you're already paying for a Claude subscription. Routing Anthropic traffic through the gateway with a subscription token instead of a per-token key changes the cost math on agentic loops that would otherwise rack up metered spend. That alone can justify a Docker deployment. Where it bites: there's real operational weight here. You need Docker, GPU drivers matched to the correct image variant (seven are published — CPU, CUDA, ROCm, Vulkan, MUSA, Intel, CANN), and disk for multi-gigabyte weights. The desktop app is single-tenant, so if you want roles and access requests, the desktop download won't
Researching BodhiApp? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Real-world workflow fit
Concrete scenarios for the personas BodhiApp actually fits — and what changes day-one when you adopt it.
You pull a quantized Llama GGUF from HuggingFace through the Models page, create an alias binding it to temperature and top-p values, and point your existing OpenAI client library at the local endpoint.
Outcome: One authenticated server serving your local model through an OpenAI-compatible API, with no code change beyond the base URL.
You run the Docker CUDA variant behind Caddy for TLS, enable OAuth2 PKCE login, and let teammates file access requests that an admin approves into User, PowerUser, and Manager roles.
Outcome: A multi-user gateway where each person signs in with OAuth and API tokens carry scopes rather than sharing one key.
You add an MCP server, create a per-user instance with whitelisted tools, test each tool in the MCP Playground, then enable the whitelist for a single conversation.
Outcome: Models invoke MCP tools mid-conversation with tool execution feedback visible in chat, scoped to just the tools you approved.
Use Cases
- Run a quantized Llama or Mistral GGUF locally and expose it through an OpenAI-compatible endpoint
- Proxy OpenAI, Anthropic, and Gemini through one authenticated server using your own API keys
- Deploy a team-wide AI gateway in Docker with OAuth2 login, four roles, and audit trails
- Give models autonomous access to MCP tools for database queries or external API calls
- Use a Claude.ai or Anthropic Console subscription through Anthropic OAuth instead of a per-token API key
- Compare GGUF quantizations side-by-side by switching model aliases without a restart
- Build a React app against Bodhi using @bodhiapp/bodhi-js-react and scoped API tokens
- Test MCP servers and individual tools in the MCP Playground before rolling them out
Limitations
- BodhiApp is self-hosted, so you run the server, reverse proxy, upgrades, and backups yourself; local GGUF models must be downloaded and stored on your own hardware, and inference speed depends on your hardware and GPU variant.
- Cloud proxying depends on your own provider API keys or subscriptions (e.g. an Anthropic OAuth Claude.ai or Anthropic Console subscription) and fails if those lapse.
- The Tauri desktop build is single-tenant, while multi-user features (roles, access requests, audit trail) require the Docker variant with auth configured.
- The Ollama compatibility layer is documented as deprecated, with OpenAI, Anthropic, and Gemini wire formats presented as the supported surfaces.
as of 2026-10-10
Verification history
We have re-verified BodhiApp 9 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-verified summary, description, our verdict, our analysis, pricing model, pricing tiers, features, integrations, who it suits, who should skip it
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
- — re-checked, vendor evidence unchanged
Showing the 6 most recent of 9 verification passes.
Free to cite with attribution — this page re-verifies continuously.
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Plans compared
For each published BodhiApp tier: who it actually fits, and what it adds vs. the previous tier. Cross-reference the cost calculator above for projected annual outlay.
Free
$0
Ideal for
Developers and teams willing to run their own server — desktop for single-user local inference, or the Docker variant for multi-user deployment with OAuth2 and role-based access.
What this tier adds
Starting tier: the full gateway at no license cost, including local GGUF inference, cloud API proxying, MCP tools, and four-role auth. Your spend is hardware, GPU time, and disk.
Where the pricing makes sense
The company stage and team size where BodhiApp's pricing actually pencils out — and where peers do it cheaper.
Bodhi App is free and open source, so the cost that matters is infrastructure, not licensing: GPU hardware or cloud GPU time, disk for multi-GB GGUF files, and engineering hours for Docker deployment, reverse-proxy TLS termination, and backups. Compare that against a managed gateway charging per token or per seat, where you trade cash for not running anything.
Setup time & first value
How long it actually takes to get something useful out of BodhiApp — broken out by persona, not the marketing-page minute.
Desktop app: minutes to install, but hours before first value if you are pulling a multi-GB GGUF file over a slow link. Docker: an afternoon for a single-user server on CPU; allow a day or more for GPU variant matching, reverse-proxy TLS termination, and OAuth2 multi-user configuration with role setup.
Switching to or from BodhiApp
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From a single-user local runtime like Ollama's own server: redirect clients to Bodhi's OpenAI Chat Completions endpoint, since the Ollama-compatible endpoints are deprecated
- →From direct OpenAI API calls: point the base URL at your Bodhi server and keep your existing OpenAI-compatible client library
- →From direct Anthropic API calls: use the Anthropic Messages compatibility layer, or switch to Anthropic OAuth if you hold a Claude.ai or Anthropic Console subscription
- →From a hand-rolled llama.cpp server: register the same GGUF file as a model and recreate your sampling settings as a Bodhi model alias
- →From separate per-provider API keys scattered across apps: consolidate them as API Models behind Bodhi's single authenticated endpoint
- ↗To a managed gateway: export your model alias parameter sets as documentation for recreating them, then re-point clients at the hosted base URL
- ↗To a vendor-hosted chat product: there is no export path for conversations — treat chat history as non-portable
- ↗To a direct provider API: replace the Bodhi base URL with the provider endpoint and re-supply the API key Bodhi was proxying
- ↗To llama.cpp directly: reuse the GGUF files in Bodhi's local cache, but rebuild the alias parameters by hand
- ↗To an Ollama workflow: not recommended as a destination, since Bodhi's own Ollama compatibility layer is deprecated
Integrations
Resources & Guides
- Documentationgetbodhi.app
Docs · BodhiApp
Full product docs from getbodhi.app
- Conceptsgetbodhi.app
Overview · BodhiApp
Core ideas explained from getbodhi.app
- Documentationgetbodhi.app
Chat · BodhiApp
Full product docs from getbodhi.app
- Documentationgetbodhi.app
Overview · BodhiApp
Full product docs from getbodhi.app
- Quickstartgetbodhi.app
Getting Started · BodhiApp
Get up and running fast from getbodhi.app
- Documentationgetbodhi.app
Docker · BodhiApp
Full product docs from getbodhi.app
- Documentationgetbodhi.app
Reverse Proxy · BodhiApp
Full product docs from getbodhi.app
- Documentationgetbodhi.app
Overview · BodhiApp
Full product docs from getbodhi.app
- Documentationgetbodhi.app
Faq · BodhiApp
Full product docs from getbodhi.app
Tutorials & Learning
YouTube returned 6 videos for “BodhiApp”, and we withheld 6: 6 could not be judged, because “BodhiApp” is a single word that other videos use for other things. We are showing none, because we could not prove any of them are about BodhiApp.
Official links
Tools that pair well with BodhiApp
Common stack mates teams adopt alongside BodhiApp, with the specific reason each pairing earns its keep.
APIMart
APIMart is a discounted AI API gateway: one OpenAI-compatible endpoint for 190+ text, image, video, and audio models, billed pay-as-you-go
Inference Engine by GMI Cloud
GMI Cloud Inference Engine runs text, image, video, and audio models behind one OpenAI-compatible API on dedicated NVIDIA GPUs.
Cortex.cpp
Run local HuggingFace models or route prompts to Claude, GPT and Gemini with your own API keys
Featured Head-to-Head Comparisons
Bodhiapp vs Spider Cloud
Spider Cloud and BodhiApp serve entirely different needs. Spider Cloud is a high-speed web scraping and crawling API optimized for feeding real-time data to AI agents and RAG pipelines, with a Rust engine and new Browser AI commands. BodhiApp is a self-hosted AI inference gateway that unifies local GGUF models and cloud APIs under a single endpoint with user management. Choose Spider Cloud if your primary need is web data extraction; choose BodhiApp if you need a privacy-first, controllable AI model server.
Bodhiapp vs Temporal Ai
Temporal AI and BodhiApp serve entirely different needs. Choose Temporal if you're building mission-critical AI agents that must survive failures and require durable orchestration with human-in-the-loop. Choose BodhiApp if you need a self-hosted, privacy-focused gateway to run local open-weight LLMs (GGUF) and proxy cloud APIs through a single OpenAI-compatible endpoint.
Bodhiapp vs Voyage Ai
Choose Voyage AI if you need high-accuracy embeddings and rerankers for enterprise RAG, especially in finance/legal domains. BodhiApp is unbeatable for teams wanting a free, self-hosted gateway to mix local GGUF models with cloud APIs, with built-in user management. They are complementary: Voyage improves retrieval quality; BodhiApp simplifies model orchestration.
Alternatives to BodhiApp
View allAPIMart
APIMart is a discounted AI API gateway: one OpenAI-compatible endpoint for 190+ text, image, video, and audio models, billed pay-as-you-go
Inference Engine by GMI Cloud
GMI Cloud Inference Engine runs text, image, video, and audio models behind one OpenAI-compatible API on dedicated NVIDIA GPUs.
Cortex.cpp
Run local HuggingFace models or route prompts to Claude, GPT and Gemini with your own API keys
Frequently Asked Questions
Best-of guides
Topics
Used BodhiApp? Help shape our editorial sentiment research.