Polyer

Open WebUI

Deploy Open WebUI on Polyer for a self-hosted chat interface to AI models through OpenAI-compatible APIs or Ollama. The template runs one public Open WebUI service with no bundled model server; its data lives on a volume at /app/backend/data. Review the floating main image tag and the model connections you will add.

AI applicationsCoolify open catalog

What you can use it for

  • Give your team a shared web chat interface for models from an OpenAI-compatible API provider.
  • Ask questions about uploaded documents with the models you connect, keeping chat history in your own deployment.

What this template creates

open-webuighcr.io/open-webui/open-webui:main
Public endpoint Persistent volume

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

  1. Select Configure deployment and sign in or create an account.
  2. Choose a new or existing project and select an available region.
  3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
  4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Operating this application

  • Create the first account as soon as the generated domain is reachable, because Open WebUI makes the first registered user an administrator. Then review sign-up settings and add model connections in the admin settings.
  • Back up the volume at /app/backend/data, which holds the database with chats, users and settings as well as uploaded files, and test restoring it.
  • The main image tag moves to newer builds on redeploy, so pin a release tag or read the release notes and back up before upgrading. Model provider API keys and inference charges are separate from hosting.

Hosting costs

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Review prices and estimate resource costs

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-10

Upstream documentation Template source and license

Choose your next step

Related templates