Fully Managed Dify
as a Service

Deploy Dify as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

Dify is an open-source platform for building LLM applications: chatbots, agents, retrieval-augmented assistants, and multi-step AI workflows, combining the convenience of a hosted AI builder with the security and control of self-hosted infrastructure. It connects to OpenAI, Anthropic, Gemini, and local models, and gives non-developers a visual canvas to ship production AI apps.

✓Free 7-day trial  ✓99.9% Uptime SLA  ✓No credit card  ✓Cancel anytime

✓Free 7-day trial  ✓99.9% Uptime SLA
✓No credit card  ✓Cancel anytime

Dify

Dify

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region — 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
Dify Preview Image

ABOUT THE SOFTWARE

What is Dify

Dify is an open-source platform for building and running LLM applications: chatbots, agents, RAG assistants, and visual AI workflows, without writing the orchestration yourself. It connects to commercial and local models alike and publishes finished apps as APIs or embeddable web widgets.

Dify is maintained by LangGenius, Inc., based in Menlo Park, California. The project passed more than 150,000 GitHub stars in 2026 and, by the maintainer's own figures, runs on more than 1.4 million machines worldwide, with over 2,000 teams and 280 organizations building on its commercial editions.

In March 2026, LangGenius raised a 30 million dollar Series Pre-A round at a 180 million dollar valuation, making Dify one of the better-capitalized open-source AI-app platforms. Its licence is Apache 2.0 with two added conditions: you may not run Dify as a shared multi-tenant service without a commercial licence, and you may not remove Dify's branding from the console. DANIAN runs one isolated instance per customer, which keeps you on the single-tenant side of that line.

FEATURES

What Dify does

Dify gives builders a visual canvas for four app types, chatbot, chatflow, agent, and workflow, backed by a knowledge base, a model gateway, a plugin marketplace, and a prompt IDE. Finished apps publish as APIs or embeddable widgets in a few clicks.

Visual app builder

Build chatbots, branching chatflows, function-calling agents, and multi-step workflows on a drag-and-drop canvas. No orchestration code; non-developers ship production apps and engineers extend them with custom nodes.

Knowledge base and RAG

Upload PDFs, Word, Markdown, CSV, and HTML, or sync from Notion and scraped pages, then retrieve against them with hybrid search. Dify handles chunking, embedding, and reranking.

Model gateway

Connect OpenAI, Anthropic, Gemini, Mistral, DeepSeek, and local models through Ollama or any OpenAI-compatible endpoint. Switch models per app without rewriting prompts.

Plugin marketplace and tools

Install tools, model providers, and extensions from the marketplace, or load your own signed packages. Plugins run in a dedicated daemon, isolated from the core app.

Agent framework

Build ReAct and function-calling agents that call tools, query your knowledge base, and chain steps. Add a human-input node when a person needs to review before the agent continues.

Publish as API or web app

Ship any app as a REST API, a hosted web page, or an embeddable chat widget for your site. Rate limits and access are yours to set on a self-hosted instance.

Prompt IDE and versioning

Draft, compare, and version prompts in a dedicated editor. Roll an app back to a previous definition, and export the whole app as portable YAML so you are never locked in.

Observability

Trace every run, inspect token use and latency, and pipe logs to external observability tools. App and conversation logs are retained so you can debug what a model actually did.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app on DANIAN ships with the same operational baseline. You do not choose a backup add-on or a monitoring tier. Hosting, patching, backups, SSL, and support are part of the €9, and they apply to Dify the same way they apply to everything else in the catalog.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers by email and ticket. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed Dify

Teams that built on OpenAI's Assistants API after its shutdown on 26 August 2026, and many are moving to Dify to own their AI apps outright. Self-hosting Dify is straightforward to start and unforgiving to keep running. Managed hosting removes the part that bites.

Running Dify is not one container; it is thirteen: the API, two Celery workers, the web frontend, Postgres, Redis, a vector database, the code sandbox, the outbound proxy, the plugin daemon, and Nginx. Each has its own version, its own failure mode, and its own place in the upgrade order.

The part that catches people is upgrades. The plugin daemon, the plugin SDK, and the Dify API have to move in lockstep, and when they don't, the console fills with "Failed to request plugin daemon" errors: a live, still-open report against v1.14.2. A separate trap: upgrading the bundled vector store can silently break every existing knowledge base until you run a migration script. We have read those threads so you don't have to.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run Dify on DANIAN

The teams that move to managed Dify are rarely AI labs. They are support groups, internal-tools teams, and small agencies who want a private Dify without standing up thirteen containers or babysitting upgrades. Three patterns we see, with the configuration choices behind them.

CONSUMER-PRODUCT SUPPORT TEAM

A support copilot grounded in the product manual

A hardware company built a customer-support assistant on Dify over its product docs, then a fleet of internal apps beside it. We would run this single-tenant in the region nearest their users, route knowledge files to object storage, and pin a Claude-class model. One documented rollout reached 200 apps in a month.

INTERNAL-TOOLS TEAM

Self-service AI apps for the whole company

A mid-size operations team wanted every department building its own bots on one shared model config, with logs kept centrally. On DANIAN that is one instance, one model gateway, pgvector reused from Postgres, and SSO fronted by a proxy. A comparable rollout hit 70 apps in its first month.

THREE-PERSON CONTENT AGENCY

An approval-gated content workflow

A small agency runs a Dify workflow that drafts briefs, then pauses on a human-input node for a copywriter to approve before publishing through their automation tool. We size the worker for batch jobs and keep their model keys in their own instance, so usage costs are theirs to control, not metered by a vendor.

COMPARISON

Four ways to run Dify

There are four realistic ways to run Dify: pay Dify's own cloud per workspace, rent a VPS and self-host, buy a home server, or let DANIAN run it for EUR 9 a month. The table below shows the cost at one, five, and ten people.

Path1 user5 users10 usersOngoing ops timeNotes
Dify Cloud (hosted by Dify)$59/mo$159/mo$159/mo0 hrsPer-workspace plans with seat caps and monthly message-credit limits. The Professional plan tops out at 3 members, so a fourth teammate forces the jump from $59 to $159.
Self-host on a VPS~$44/mo~$44/mo~$44/mo1–2 hrs/moA $24/mo, 2 vCPU / 4 GB production-class VPS, plus object-storage backup and monitoring. 4 GB is Dify's floor; production comfortably wants 8 GB or more. Add your time for patching, upgrades, and backups: EUR 60–240/mo.
Home serverEUR 18–55/mo*EUR 18–55/mo*EUR 18–55/mo*2–4 hrs/moA Synology DS923+ (~EUR 650) or HP ProLiant ML30 Gen10 (~EUR 800–1,500), amortized, plus electricity, a static-IP business line, and off-site backup. EUR 210–667/mo effective once power, connectivity, and your time are counted.
DANIAN managed DifyEUR 9/moEUR 9/moEUR 9/mo0 hrsFlat per app, any number of users. Backups, version upgrades, monitoring, SSL, and human support included, in the region you choose.

Dify Cloud prices are list USD from dify.ai/pricing: roughly EUR 55 and EUR 148. VPS and home-server figures combine infrastructure with an estimate of operator time at EUR 60–120/hour. *Home-server hardware shown amortized over 36 months; the effective monthly total is higher once electricity, a business internet line, and off-site backup are added.

BY INDUSTRY

Dify for specific industries

Different industries put different demands on an AI-app platform: where the data may live, who signs off on model output, and how long logs are kept. These four come up most for Dify, each with the configuration choice we make for it.

The constraint here is a licensing one as much as a data one. If you embed Dify-built AI inside your own product for many customers, you are operating it multi-tenant, which Dify's licence restricts without a commercial agreement. So the pattern we run for software teams is the internal one: a single-tenant Dify for your own engineers and support staff, isolated per company, with Dify branding left intact per the licence. A typical app is a Slack-embedded copilot that answers over your product docs, issue tracker, and runbooks, with tool calls into internal services. Dify itself reports more than 2,000 teams and 1.4 million machines running it, so the platform is well past early-adopter risk for production internal tooling.

Support teams care most about where conversation data lives and keeping a person in the loop on anything sensitive. On DANIAN we deploy the instance in the region closest to the support team, route knowledge-base files and transcripts to object storage so nothing important sits only on a container disk, and wire a human-handoff step into the flow. The workflow is usually tier-one deflection: a chatbot grounded in the product manual and help-centre answers the common questions and escalates the rest with full context attached. One documented consumer-electronics rollout built a working support bot in two days and processed 50,000 customer reviews a month through Dify, against 15,000 done by hand.

Education teams work under strict expectations about student-record handling and human review of anything that affects a grade. For this we pin the instance to a single region, turn on app version control so every scoring prompt is recorded and reversible, and build a mandatory review step before any result is committed. A common workflow is rubric-grounded short-answer scoring: the model drafts a score and rationale against the rubric in the knowledge base, and a teacher approves or overrides before it is final. ETS, the testing organization, builds these pipelines on Dify and reports faster delivery at lower cost; classroom pilots report several hours a week saved on routine marking.

Internal platform teams standardize how non-developers build AI apps: one approved model configuration, role-based access, and logs kept long enough to review how a decision was made. On DANIAN that is a single shared instance with one model gateway, user roles managed in Dify, and single sign-on fronted by an identity proxy, since native SSO is reserved for Dify's enterprise edition. The workflow is a catalogue of department bots: HR policy, IT help, finance questions, each a small app over its own knowledge base, all on the same backend. One operations team reached roughly 950 internal apps and three-quarters of staff signed up within months, after a product-data extractor went live in about three hours.

FAQ

Frequently asked questions

Three groups of questions: the technical details of running Dify, how migration and onboarding work, and the billing and platform basics. If yours isn't here, chat or email us; a person who runs Dify will answer. We keep the answers specific and current to the v1.17 release line.

01

Technical and configuration

Effectively all of them. Dify connects to OpenAI, Anthropic, Gemini, Mistral, and DeepSeek, plus local models through Ollama or any OpenAI-compatible endpoint: over 100 in total. You set providers per app or per workspace, and you bring your own API keys, so model spend is billed by the provider, not by us.
PDF, Word, Markdown, plain text, CSV, and HTML, plus Notion sync and webpage scraping. Dify chunks, embeds, and reranks them for retrieval.
By default we reuse Postgres with pgvector rather than running a separate Weaviate container. It lowers the memory floor and sidesteps the v3-to-v4 Weaviate migration that breaks knowledge bases on upgrade.
A chatbot is a single-prompt conversation. A chatflow is a chatbot on a visual canvas with branching and tool calls. A workflow is a non-conversational pipeline (one input, a graph of nodes, an output) that you publish as an API. An agent calls tools and reasons over steps.
Yes. Any app publishes as a REST API. Dify imposes no rate limit on a self-hosted instance; you set your own at the proxy.
No. Dify's licence requires its branding to stay in the console, and removing it needs Dify's own enterprise licence, which we do not resell. You get a fully private, single-tenant instance on your own domain, but the Dify console keeps Dify's logo. We would rather tell you that up front than break the licence.
No. Every customer gets an isolated Dify instance with its own containers, database, and storage: one tenant, one workspace. Nothing about your apps, prompts, or knowledge base shares a process with anyone else, which also keeps you on the single-tenant side of Dify's licence.

02

Migration and onboarding

21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on email and the ticket section in the client portal. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 email and ticket support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed Dify for 7 days

No card. Cancel from the dashboard.