AI & Models · Integration
Open WebUI
Add Open WebUI to your product for your customers, and give your AI agents governed access to it.
Embed an Open WebUI integration so customers who run their own models can point your product at their own deployment rather than sending content to a hosted provider. Open WebUI is the self-hosted, open-source interface teams put in front of local and remote models, and it exposes an OpenAI-compatible API for model listing and chat completions plus endpoints for uploading files and working with knowledge collections. Each customer supplies their own instance URL and API key, so requests stay inside their environment and run under their credentials rather than a shared account. fastn owns the credential storage, retries and API upkeep, and the same governed connection is what your AI agents use.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let customers point your product at their own self-hosted Open WebUI instance so AI features run against models they control.
List the models a customer's deployment actually serves so your product offers what is really available rather than a fixed list.
Run chat completions through the customer's own instance so content never leaves the environment their policy allows.
Add files to a customer's knowledge collection so retrieval answers draw on their own material.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent runs a completion against the customer's self-hosted instance within scoped permissions, with each call logged.
An agent adds a document to a knowledge collection so later questions are answered from that tenant's own content.
An agent reports which models a customer's deployment currently exposes before a workflow picks one.
Example prompt
Ask our self-hosted Open WebUI instance to summarise this document and tell me which model answered.
Set up Open WebUI in 4 steps
- 01Enable the Open WebUI connector in your fastn dashboard.
- 02Have each customer supply their own instance URL and API key so calls run inside their environment.
- 03Configure the models, prompts and knowledge collections your product uses, per customer.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Open WebUI integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Open WebUI integration without building it. Your customers connect their own Open WebUI account inside your product and work their models, requests and outputs there, with no per-customer code on your side.
- Handle the part that actually costs time: per-customer keys, quotas and cost attribution matter more than schema here, because every call is billed. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Open WebUI update is not your on-call problem.
- One integration serves your product and your agents. The same governed Open WebUI connection powers in-product features and gives AI agents scoped, audited access, so you give your product and your agents a model call each customer pays for themselves without wiring it twice.
Used by these teams
Compare with
OpenAI
Anthropic Claude
Hugging FaceOften used alongside
Tools the same teams tend to run next to Open WebUI, across other categories.
Snowflake
Airtable
PostgreSQL
AmplitudeOpen WebUI integration FAQ
How do I add an Open WebUI integration to my product?
Enable the Open WebUI connector in your fastn dashboard, then let each customer authenticate their own Open WebUI account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Open WebUI client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Open WebUI account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Open WebUI account and only ever sees their own models, requests and outputs. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Open WebUI integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent runs a completion against the customer's self-hosted instance within scoped permissions, with each call logged.
Who maintains the Open WebUI integration?
fastn does. When Open WebUI changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Whose Open WebUI API key and quota does each call use?
Each customer authorises their own Open WebUI account, so usage, rate limits and cost land on the customer that caused them. You are not metering a shared key and re-billing it, and one heavy customer cannot exhaust another's quota.
Are inputs and outputs auditable?
Yes. Every call is logged per tenant with the call, the input and the result, so an output can be traced back to what produced it. That matters more here than in most integrations, because a generated answer or an extracted field cannot be reconstructed from the request alone.
What can I build with the Open WebUI integration?
A common starting point: point your product at their own self-hosted Open WebUI instance so AI features run against models they control. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Open WebUI integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Open WebUI does not change your per-connector cost. You can start free with 3 connected accounts.
Add Open WebUI to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.