AltFreeStack
ESEN
Artificial Intelligencedocker-readypermissive-licenseOpen-Core🔴 Full · ~2GB💾 Recommended storage: 40GB

Dify: Open-Core alternative to OpenAI API in 2026

Dify is a platform for designing, testing and deploying AI applications (chatbots, agents, flows) with a visual editor and built-in observability, instead of building everything on the raw OpenAI API by hand.

Core is open source, but advanced features or enterprise support may be behind a paid tier — check the license.

ℹ️ 40GB is the project's official recommendation for a production deployment (covers Postgres, Redis and the rest of the stack). No GPU of its own required — it only helps if you connect a local embeddings/inference runtime.

Alternative to OpenAI API
License Apache-2.0158.4k starsWebsite GitHub Repository

Audit Snapshot

View notes →

  • License — Not verifiable on GitHub

  • GitHub — Active

  • Latest release — 1.17.1 · 1 month ago

  • Docker Compose — Partial

  • Production — Not production-tested by AltFreeStack

Dify vs. OpenAI API

Pros

  • Cuts down a lot of the code needed to ship an AI product

Things to consider

  • Full production stack has several services (Weaviate/Redis)

Quick Docker installation guide

Copy this docker-compose.yml, adjust the example passwords and run docker compose up -d on your server. See the full step-by-step guide →

💡 Official SaaS or self-hosted with AltFreeStack?

  • On the official cloud: a recurring monthly fee and usage limits on OpenAI API.
  • On your own VPS: the core is free to self-host on your own server — no more monthly SaaS fee, though some advanced features stay behind a paid plan.
docker-compose.yml
version: "3.9"
services:
  dify-api:
    image: langgenius/dify-api:1.17.1
    restart: unless-stopped
    ports:
      - "5001:5001"
    environment:
      - DB_HOST=dify-db
      - DB_USERNAME=dify
      - DB_PASSWORD=change-me-postgres-password # must match POSTGRES_PASSWORD below
      - REDIS_HOST=dify-redis
    depends_on:
      - dify-db
      - dify-redis
  dify-db:
    image: postgres:15-alpine
    restart: unless-stopped
    environment:
      - POSTGRES_USER=dify
      - POSTGRES_PASSWORD=change-me-postgres-password # REQUIRED: generate a random secret before first run
      - POSTGRES_DB=dify
    volumes:
      - dify_pg_data:/var/lib/postgresql/data
  dify-redis:
    image: redis:7-alpine
    restart: unless-stopped
volumes:
  dify_pg_data:

🚀 Deploy in 1 command

Recommended for beginners

Copy this single command and paste it into your freshly created VPS's console (Vultr, DigitalOcean...). It downloads the script, prints it to your screen so you can see exactly what it's about to do (never a blind direct pipe), and only then installs Docker if needed, writes the files with secrets already generated, and starts everything — no nano, no pasting code blocks.

curl -sSL ".../api/deploy?stack=dify" -o deploy.sh && cat deploy.sh && bash deploy.sh
See what this script does →

This docker-compose corresponds to an actively maintained project — last commit today.

This docker-compose not working for you? Report it on GitHub →

Technical profile

License
Apache-2.0
Category
Artificial Intelligence
Replaces
OpenAI API
Tech stack
PythonNext.jsPostgreSQL

Under the hood

Database

PostgreSQL

Language

Python

Platforms

Web

Key features

  • Visual editor for AI agents and flows
  • Observability and logs for every conversation
  • Multi-model: OpenAI, Anthropic, local

Preview

Dify interface preview

Public image provided by Dify on its own website.

💾 Backups in 3 steps (Day 2)

As long as the ./data folder (the "volume" mapped into the container) exists on your server, your data survives any restart or container update — that's the only thing you need to back up.

1. Create a compressed backup on the server

tar -czvf backup-$(date +%F).tar.gz ./data

2. Download it to your computer

From your computer's terminal (not your server's):

scp root@YOUR_IP:~/app/backup-*.tar.gz ./

3. Restore in case of emergency

tar -xzvf backup-file.tar.gz
🌐 Connect your domain with free SSL

Step 1 — Set up the DNS

In your domain registrar's dashboard (Cloudflare, Namecheap, GoDaddy...), create a record:

Type
A
Name/Host
@ (root domain) or a subdomain, e.g. app
Content/Value
Your server's public IP

Wait 5 to 15 minutes for the record to propagate across the internet.

Step 2 — Automatic reverse proxy with Caddy

One single file, no Nginx config or manual certificates — Caddy issues and renews Let's Encrypt HTTPS on its own.

Create a file called Caddyfile:

yourdomain.com {
    reverse_proxy localhost:5001
}

Start Caddy with this command (pulls the image and runs it in the background):

docker run -d -p 80:80 -p 443:443 --name caddy --restart always -v $PWD/Caddyfile:/etc/caddy/Caddyfile -v caddy_data:/data caddy