exploreAIExplore
How to Use Dify for Self-host vs cloud choices
Learn Dify self-host vs cloud choices with step by step workflows, realistic examples, and verified plan notes.
Dify works well for self-host vs cloud choices when you run it like production work: locked brief, SOURCE facts, then review before publish. Dify is an open-source LLM application platform for building chatbots, agents, and workflows with visual orchestration, RAG, and model management, with self-hosting and cloud options. Confirm live plans on dify.ai. Start at /explore/dify.
This guide focuses on self-host vs cloud choices in detail. Related Dify articles: /blog/how-to-use-dify-for-human-handoff-fallbacks, /blog/how-to-use-dify-for-spend-and-key-practices, /blog/how-to-use-dify-for-content-filter-setups.
When this workflow is the right job
Use self-host vs cloud choices when the deliverable is specifically this Dify job. Switch to visual chatbot builds when that workflow already owns the asset.
Step by step workflow
1. Brief Self-host vs cloud choices
Write what must stay true for self-host vs cloud choices in Dify before settings or spend.
Brief: Self-host vs cloud choices Keep: verified SOURCE facts only Avoid: invented pricing or features Success: one reviewable output
2. Open Dify for Self-host vs cloud choices
Use the Dify surface that owns self-host vs cloud choices. Do not mix a neighboring workflow in the same pass.
Surface: Self-host vs cloud choices Start: pilot with one representative input Plans: dify.ai
3. Pilot Self-host vs cloud choices
Run a single self-host vs cloud choices pilot. Score clarity, grounding, and whether the output is reviewable.
Pilot: Self-host vs cloud choices [ ] SOURCE facts match [ ] Output reviewable [ ] Settings logged
4. Refine Self-host vs cloud choices
Change one self-host vs cloud choices dimension only. Save a template from the best run.
Refine: Self-host vs cloud choices Change: one control only Keep: SOURCE and success criteria
Practical self-host vs cloud choices examples
Private agent
Scenario: A team sets up Self-host vs cloud choices in Dify for "Private agent". Objective: Stand up a citation-aware workspace/agent for Private agent with clear refuse-if-missing behavior. Inputs: - Document set for Private agent - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Private agent → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Private agent with sample Q&A, citations, and known gaps.
Embed mode
Scenario: A team sets up Self-host vs cloud choices in Dify for "Embed mode". Objective: Stand up a citation-aware workspace/agent for Embed mode with clear refuse-if-missing behavior. Inputs: - Document set for Embed mode - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Embed mode → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Embed mode with sample Q&A, citations, and known gaps.
Secure weights dir
Scenario: A team sets up Self-host vs cloud choices in Dify for "Secure weights dir". Objective: Stand up a citation-aware workspace/agent for Secure weights dir with clear refuse-if-missing behavior. Inputs: - Document set for Secure weights dir - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Secure weights dir → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Secure weights dir with sample Q&A, citations, and known gaps.
Chunk size note
Scenario: A team sets up Self-host vs cloud choices in Dify for "Chunk size note". Objective: Stand up a citation-aware workspace/agent for Chunk size note with clear refuse-if-missing behavior. Inputs: - Document set for Chunk size note - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Chunk size note → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Chunk size note with sample Q&A, citations, and known gaps.
Top-k retrieval
Scenario: A team sets up Self-host vs cloud choices in Dify for "Top-k retrieval". Objective: Stand up a citation-aware workspace/agent for Top-k retrieval with clear refuse-if-missing behavior. Inputs: - Document set for Top-k retrieval - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Top-k retrieval → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Top-k retrieval with sample Q&A, citations, and known gaps.
Refuse if missing
Scenario: A team sets up Self-host vs cloud choices in Dify for "Refuse if missing". Objective: Stand up a citation-aware workspace/agent for Refuse if missing with clear refuse-if-missing behavior. Inputs: - Document set for Refuse if missing - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Refuse if missing → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Refuse if missing with sample Q&A, citations, and known gaps.
Source quote
Scenario: A team sets up Self-host vs cloud choices in Dify for "Source quote". Objective: Stand up a citation-aware workspace/agent for Source quote with clear refuse-if-missing behavior. Inputs: - Document set for Source quote - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Source quote → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Source quote with sample Q&A, citations, and known gaps.
Update ingest
Scenario: A team sets up Self-host vs cloud choices in Dify for "Update ingest". Objective: Stand up a citation-aware workspace/agent for Update ingest with clear refuse-if-missing behavior. Inputs: - Document set for Update ingest - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Update ingest → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Update ingest with sample Q&A, citations, and known gaps.
Access roles
Scenario: A team sets up Self-host vs cloud choices in Dify for "Access roles". Objective: Stand up a citation-aware workspace/agent for Access roles with clear refuse-if-missing behavior. Inputs: - Document set for Access roles - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Access roles → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Access roles with sample Q&A, citations, and known gaps.
Docker deploy
Scenario: A team sets up Self-host vs cloud choices in Dify for "Docker deploy". Objective: Stand up a citation-aware workspace/agent for Docker deploy with clear refuse-if-missing behavior. Inputs: - Document set for Docker deploy - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Docker deploy → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Docker deploy with sample Q&A, citations, and known gaps.
Desktop install
Scenario: A team sets up Self-host vs cloud choices in Dify for "Desktop install". Objective: Stand up a citation-aware workspace/agent for Desktop install with clear refuse-if-missing behavior. Inputs: - Document set for Desktop install - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Desktop install → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Desktop install with sample Q&A, citations, and known gaps.
Test prompt small
Scenario: A team sets up Self-host vs cloud choices in Dify for "Test prompt small". Objective: Stand up a citation-aware workspace/agent for Test prompt small with clear refuse-if-missing behavior. Inputs: - Document set for Test prompt small - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Test prompt small → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Test prompt small with sample Q&A, citations, and known gaps.
Pin model version
Scenario: A team sets up Self-host vs cloud choices in Dify for "Pin model version". Objective: Stand up a citation-aware workspace/agent for Pin model version with clear refuse-if-missing behavior. Inputs: - Document set for Pin model version - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Pin model version → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Pin model version with sample Q&A, citations, and known gaps.
PII redaction
Scenario: A team sets up Self-host vs cloud choices in Dify for "PII redaction". Objective: Stand up a citation-aware workspace/agent for PII redaction with clear refuse-if-missing behavior. Inputs: - Document set for PII redaction - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for PII redaction → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for PII redaction with sample Q&A, citations, and known gaps.
Eval questions
Scenario: A team sets up Self-host vs cloud choices in Dify for "Eval questions". Objective: Stand up a citation-aware workspace/agent for Eval questions with clear refuse-if-missing behavior. Inputs: - Document set for Eval questions - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Eval questions → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Eval questions with sample Q&A, citations, and known gaps.
Handoff human
Scenario: A team sets up Self-host vs cloud choices in Dify for "Handoff human". Objective: Stand up a citation-aware workspace/agent for Handoff human with clear refuse-if-missing behavior. Inputs: - Document set for Handoff human - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Handoff human → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Handoff human with sample Q&A, citations, and known gaps.
HR policy workspace
Scenario: A team sets up Self-host vs cloud choices in Dify for "HR policy workspace". Objective: Stand up a citation-aware workspace/agent for HR policy workspace with clear refuse-if-missing behavior. Inputs: - Document set for HR policy workspace - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for HR policy workspace → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for HR policy workspace with sample Q&A, citations, and known gaps.
Citations on
Scenario: A team sets up Self-host vs cloud choices in Dify for "Citations on". Objective: Stand up a citation-aware workspace/agent for Citations on with clear refuse-if-missing behavior. Inputs: - Document set for Citations on - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Citations on → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Citations on with sample Q&A, citations, and known gaps.
Support billing agent
Scenario: A team sets up Self-host vs cloud choices in Dify for "Support billing agent". Objective: Stand up a citation-aware workspace/agent for Support billing agent with clear refuse-if-missing behavior. Inputs: - Document set for Support billing agent - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Support billing agent → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Support billing agent with sample Q&A, citations, and known gaps.
Local model RAM
Scenario: A team sets up Self-host vs cloud choices in Dify for "Local model RAM". Objective: Stand up a citation-aware workspace/agent for Local model RAM with clear refuse-if-missing behavior. Inputs: - Document set for Local model RAM - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Local model RAM → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Local model RAM with sample Q&A, citations, and known gaps.
Vector DB pick
Scenario: A team sets up Self-host vs cloud choices in Dify for "Vector DB pick". Objective: Stand up a citation-aware workspace/agent for Vector DB pick with clear refuse-if-missing behavior. Inputs: - Document set for Vector DB pick - Model/embed choices - Access roles - Eval questions Workflow: Create workspace → Ingest docs → Configure retrieval → Test Self-host vs cloud choices questions for Vector DB pick → Tune → Hand off Requirements: - Stay within verified Dify capabilities; do not invent features. - Confirm live plan notes on dify.ai before promising volume. - Change one variable between iterations. - Human-review before external publish, send, billing, or clinical/legal use. - Require citations; refuse when unsupported. Expected output: A working Self-host vs cloud choices setup for Vector DB pick with sample Q&A, citations, and known gaps.
How to improve self-host vs cloud choices
Cut noise from self-host vs cloud choices by removing extra adjectives while preserving SOURCE facts in Dify.
Raise quality by insisting on a single success check before debating style.
Make review easier by labeling fields that must never change.
Speed iteration by cloning the last good run and altering only one control.
Stabilize outputs by pinning settings after the pilot is approved.
Reduce rework by rejecting drafts that invent claims.
Improve handoffs by recording which control produced the best result.
Harden the workflow by testing an incomplete input before trusting defaults.
Prompting and usage guidance
Name the self-host vs cloud choices job, audience, and success check before opening Dify.
Paste only verified facts under SOURCE so Dify cannot invent details.
Specify the deliverable shape up front.
Call out fixed details versus flexible style choices.
Ask Dify to flag unsupported claims before you accept the draft.
Limitations to respect
Check Dify plan gates for self-host vs cloud choices on dify.ai before you promise timelines.
Keep drafts unpublished until a human confirms SOURCE facts.
Dify can be wrong. Treat self-host vs cloud choices as provisional until review.
If documentation is silent on a claim, leave it out rather than guessing.
Practical tips for this workflow
Pilot once before batching self-host vs cloud choices in Dify.
Keep a reusable template with variables for self-host vs cloud choices.
Separate creative instructions from SOURCE facts.
Log settings from the best run.
Common mistakes
- Skipping the pilot run before scaling volume
- Inventing pricing, quotas, or features not on official pages
- Mixing unrelated workflows in one session
- Publishing without a human review gate
Treat self-host vs cloud choices in Dify as a production workflow: brief, pilot, refine, then ship with review. Related reading: /blog/how-to-use-dify-for-human-handoff-fallbacks, /blog/how-to-use-dify-for-spend-and-key-practices, /blog/how-to-use-dify-for-content-filter-setups.