Sovereignty · 2026-09-15 · 1:42

Dify: an LLM app platform you can run on your own server

Name: Dify: an LLM app platform you can run on your own server
Uploaded: 2026-09-15
Duration: 1 min 42 s
Description: sovereignty here is not "no vendor". It is "no one can switch you off". Worth the ops budget, if you actually allocate one.

Dify puts a workflow canvas, RAG, agents and model management in one open-source platform you self-host with Docker Compose. Version 1.17.1 shipped in September 2026; about 156k GitHub stars.

In favour

Prompts, documents and user data stay on your infrastructure; no feature gap against the cloud plans.
Model-agnostic, including local models via Ollama or vLLM, so the escape route is built in.

Worth watching

Apache 2.0 with two conditions: no multi-tenant offering, console branding stays.
A multi-container stack (Postgres, Redis, a vector database, several app services) with frequent releases is a real ops load; expose the agent sandbox to trusted users only.

Our takesovereignty here is not "no vendor". It is "no one can switch you off". Worth the ops budget, if you actually allocate one.

Source: Dify (LangGenius, GitHub)

← All Focus posts

AI-narrated · AI-generated content

Transcript

Before you build on a platform someone else runs, one question is worth asking. Could the whole platform run on a server you control? One open-source platform puts it in one place. A workflow canvas, retrieval-augmented generation, agents, and model management, self-hosted in containers on your own server. So the platform is not rented. It runs where you put it. A new version shipped in September 2026, and it has about 156k stars on GitHub. What that buys you. Prompts, documents and user data stay on your own infrastructure, not on someone else's. And there is no feature gap against the cloud plans. It is also model-agnostic, including local models served on your own hardware. So the escape route is built in. You are not tied to one model provider. Two things to watch. The licence is Apache 2.0, with two conditions. No multi-tenant offering. And the console branding stays. And it is a multi-container stack. Two data stores, a vector database, several app services, and frequent releases. That is a real ops load. Expose the agent sandbox to trusted users only. So sovereignty here is not “no vendor”. It is “no one can switch you off”. Worth the ops budget, if you actually allocate one.