# Templates A template is a ready-made app that Kilby deploys for you: a chat interface for language models, a vector database, a workflow tool, a model server. You pick one, read what it will create, and click **Deploy**. What it creates are ordinary Kilby services: afterwards you can change their settings, environment and instance type like any other service. There are 17 templates. Every one runs a public image pinned to one version tag, so a deploy always runs the version that was checked. Nothing is built. ## Deploy one 1. In the dashboard click **New**, then **Template** (or open [/dashboard/templates](/dashboard/templates)). Filter by category or search by name. 2. Open a template. Its page shows exactly what will be created in your workspace: each service with its image, port, disk, health check and environment variables, and what it costs at list prices. 3. Choose the names if you do not like the suggested ones. A name cannot be changed later, and it becomes part of the address (a web service) or the address other services use (a private service). 4. Fill in the settings the template asks for, if any (see below). 5. Look at the **Fits in ?** box on the side of the page. It shows each limit before and after the deploy, and says "No" if the template would go over one. 6. Click **Deploy**. Kilby creates the services, starts their first deploys and takes you to the main one. The side of the page also has **Good to know** (what to know before deploying: speed, limits, who can reach it) and **After you deploy** (the first login, where the data lives, how other services reach it). A template that fills a workspace says so on its card, before you open it, worked out from the template and from your workspace's limits: "Uses the whole workspace on the beta limits." When it does not fit next to what the workspace already runs, the refusal counts the whole template: the total that would be reserved, what your other services and databases already reserve, and what the template needs. ### Who can claim a template first A template with a public address is open to whoever finds it. Where the app can make its administrator from the environment, the template does that with a password Kilby generates, which you read under **Environment** in the service, so nobody can claim it first. Where the app has no such setting, its card and its page say so: "The first person to open this address becomes its admin: open it right after the deploy." A deploy creates **all** of the template's services or **none**: if a later one cannot be created, what was already created is deleted again. If the workspace is already using a name, the deploy is refused with "This workspace already has a service named . Choose another name." ## Which templates exist | Template | What it is | What it creates | List price | |---|---|---|---| | **NeuraTensor** (`neuratensor`) | Serve your own NeuraTensor model, a spiking state-space sequence model, behind an API key. On CPU. | Model server: private service, Standard, 5 GB disk | $26.25 a month | | **Open WebUI** (`open-webui`) | A chat interface for language models, with accounts, history and document upload. | Chat interface: web service, Standard, 5 GB disk | $26.25 a month | | **Open WebUI with Ollama** (`open-webui-ollama`) | Open WebUI and a private Ollama server, wired together. llama3.2:1b fits in the model server's 2 GB; llama3.2:3b does not. | Model server: private service, Standard, 10 GB disk; Chat interface: web service, Standard, 5 GB disk | $53.75 a month | | **LiteLLM Proxy** (`litellm`) | One OpenAI-compatible API in front of OpenAI, Anthropic and more, with a single key. | Gateway: web service, Standard | $25 a month | | **Ollama (CPU)** (`ollama`) | Run small open models on CPU as a private service your other services call. llama3.2:1b fits in its 2 GB; llama3.2:3b does not. | Model server: private service, Standard, 10 GB disk | $27.50 a month | | **Flowise** (`flowise`) | Build AI agents and chat flows on a canvas, and serve each one as an API. | Flow builder: web service, Standard, 5 GB disk | $26.25 a month | | **Langflow** (`langflow`) | Build AI agents and retrieval flows on a canvas, behind a sign-in, and serve each one as an API. | Flow builder: web service, Standard, 5 GB disk | $26.25 a month | | **SearXNG** (`searxng`) | A private web search API for your agents and chat tools, without tracking. | Search server: private service, Standard | $25 a month | | **Text Embeddings Inference (CPU)** (`text-embeddings`) | An embeddings server for retrieval apps, as a private service with an API key. | Embeddings server: private service, Standard, 5 GB disk | $26.25 a month | | **Qdrant** (`qdrant`) | A vector database with a REST API and an API key, on its own disk. | Vector database: private service, Starter, 5 GB disk | $10.25 a month | | **Chroma** (`chroma`) | A simple vector database for prototypes and small retrieval apps. | Vector database: private service, Starter, 5 GB disk | $10.25 a month | | **n8n** (`n8n`) | Workflow automation with hundreds of integrations and AI nodes. | Workflow editor: web service, Standard, 5 GB disk | $26.25 a month | | **Valkey** (`valkey`) | A Redis-compatible key-value store with a password and a disk. | Key-value store: private service, Starter, 1 GB disk | $9.25 a month | | **Static page (nginx)** (`static-page`) | A web page served by nginx. The quickest way to see a deploy work. | Web page: web service, Starter | $9 a month | | **Uptime Kuma** (`uptime-kuma`) | Monitor your sites and APIs and get alerts when they go down. | Monitor: web service, Starter, 1 GB disk | $9.25 a month | | **vLLM (GPU)** (`vllm`) | A fast OpenAI-compatible server for open models, on a GPU. | Model server: private service, GPU L4, 30 GB disk | from $1.20 per GPU hour (not deployable here now) | | **Ollama (GPU)** (`ollama-gpu`) | Run open models on a GPU as a private service. | Model server: private service, GPU L4, 30 GB disk | from $1.20 per GPU hour (not deployable here now) | Prices are list prices for a whole month, disk included. **Kilby is free during the beta and nothing is billed today.** These cannot be deployed here now: - `vllm`: Needs a GPU instance type, which is not available yet. - `ollama-gpu`: Needs a GPU instance type, which is not available yet. GPU instance types are not available yet, so the templates that need a GPU are listed but cannot be deployed. A template that needs a disk can only be deployed when disks are turned on in this Kilby. ### Settings a template asks for | Template | Setting | Required | Secret | What it is | |---|---|---|---|---| | `open-webui` | `WEBUI_ADMIN_EMAIL` | Yes | No | Administrator email. The email you will sign in with, which becomes the administrator account. | | `open-webui-ollama` | `WEBUI_ADMIN_EMAIL` | Yes | No | Administrator email. The email you will sign in with, which becomes the administrator account. | | `litellm` | `OPENAI_API_KEY` | No | Yes | OpenAI API key. Lets the gateway call openai/* models. | | `litellm` | `ANTHROPIC_API_KEY` | No | Yes | Anthropic API key. Lets the gateway call anthropic/* models. | | `text-embeddings` | `MODEL_ID` | No | No | Model. The Hugging Face model to serve. It has to be one that Text Embeddings Inference supports. | | `static-page` | `PAGE_TITLE` | No | No | Page title. The heading of the page. | | `vllm` | `HF_TOKEN` | No | Yes | Hugging Face token. Needed only for models that ask you to accept a license. | A setting is set as that environment variable of the service. A **secret** one is stored encrypted like every variable: a person with the `secrets` permission can reveal it under **Environment**, and the API and the CLI never return it. Keys and passwords that a template needs but you do not choose (a database key, a session secret) are **generated** by Kilby when you deploy and stored the same way: read them under **Environment** in the dashboard. ## Limits and permissions - Deploying a template needs the same permission as creating a service: a **Developer** or better, with an account that is enabled for deploys. A Viewer can read the gallery and a template's page. - Every limit of the workspace applies, checked for the whole template before anything is created: see [Limits and quotas](/docs/limits.md). A template that does not fit is not deployed at all, and the message names the limit, the same as when you create a service by hand. - Each service of a template counts as a service of the workspace. ## With the command line ```sh kilby templates # the gallery, with what each creates and its price kilby templates get qdrant # one template in full kilby templates deploy open-webui --name team-chat --set WEBUI_ADMIN_EMAIL=you@example.com kilby templates deploy open-webui-ollama --name team-chat --name-for ollama=team-models --set WEBUI_ADMIN_EMAIL=you@example.com OPENAI_API_KEY=... kilby templates deploy litellm --set OPENAI_API_KEY ``` A secret setting is never taken from a flag: `--set NAME` alone reads the environment variable `NAME`. The keys to name the other services of a template are: | Template | Key | Service | Suggested name | Main service | |---|---|---|---|---| | `open-webui-ollama` | `ollama` | Model server (private service) | `ollama` | | | `open-webui-ollama` | `web` | Chat interface (web service) | `open-webui` | yes (`--name`, `name`) | ## With the API ```sh curl -sS -H "Authorization: Bearer $KILBY_API_KEY" https://onkilby.com/api/v1/templates curl -sS -X POST https://onkilby.com/api/v1/templates/open-webui/deploy \ -H "Authorization: Bearer $KILBY_API_KEY" -H "Content-Type: application/json" \ -d '{"name": "team-chat", "inputs": {"WEBUI_ADMIN_EMAIL": "you@example.com"}}' ``` `GET /api/v1/templates` lists the gallery, with `available` and, when it is false, `unavailable_reason`. `POST /api/v1/templates//deploy` takes the optional `name`, `names` (by service key) and `inputs` (by variable name), needs the `deploy` permission, answers `201` with the services it created, and follows the same limits as the dashboard: `409 conflict` for a name already in use and `422 invalid_request` for a setting that is not valid, a template that is not available here, or services that do not fit. The MCP server has the tools `list_templates` and `deploy_template`: see [Use Kilby from an AI agent](/docs/agents.md). ## The Deploy to Kilby button Every template's page has a **Deploy to Kilby** button for your README, a blog post or your docs. It links to the template's page. Whoever clicks it signs in (or signs up) and comes back to that page, and can deploy from there. The Markdown for the button of a template looks like this: ```md [![Deploy to Kilby](https://onkilby.com/static/deploy-to-kilby.svg)](https://onkilby.com/dashboard/templates/open-webui) ``` The page of each template shows the Markdown and the HTML to copy. ## Related - [Services](/docs/services.md): what a template creates, and how to change it afterwards. - [Environment variables and secrets](/docs/environment.md): where the generated keys are. - [Limits and quotas](/docs/limits.md): why a template may not fit. - [Use Kilby from an AI agent](/docs/agents.md): deploy a template from an agent.