AltFreeStack
ESEN
Productivitydocker-ready100% FOSS🟡 Standard · ~1GB

Joplin: Open Source alternative to Evernote in 2026

Joplin combines Markdown notes with optional end-to-end encryption and native desktop, mobile and web apps, synced against your own server (Joplin Server), as a free alternative to Evernote.

Alternative to EvernoteAlternative to OneNote
License AGPL-3.056.7k starsWebsite GitHub Repository

Audit Snapshot

View notes →

  • License — Not verifiable on GitHub

  • GitHub — Active

  • Latest release — v3.7.21 · 17 days ago

  • Docker Compose — Partial

  • Production — Not production-tested by AltFreeStack

Joplin vs. Evernote

Pros

  • Real end-to-end encryption, not just in transit
  • Mature native apps on all 3 major platforms

Things to consider

  • Running your own sync server (Joplin Server) is an extra step compared to the paid cloud
  • Interface is more functional than visually polished

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 Evernote.
  • On your own VPS: 100% free software on your own server, with no artificial row, project or user limits.
docker-compose.yml
services:
  joplin-server:
    image: joplin/server:3.7.2
    restart: unless-stopped
    ports:
      - "22300:22300"
    environment:
      APP_BASE_URL: http://localhost:22300 # CHANGE THIS TO YOUR DOMAIN
      DB_CLIENT: pg
      POSTGRES_HOST: joplin-db
      POSTGRES_DATABASE: joplin
      POSTGRES_USER: joplin
      POSTGRES_PASSWORD: change-me-postgres-password # REQUIRED: generate a random secret before first run
    depends_on:
      - joplin-db
  joplin-db:
    image: postgres:16-alpine
    restart: unless-stopped
    environment:
      POSTGRES_USER: joplin
      POSTGRES_PASSWORD: change-me-postgres-password # must match POSTGRES_PASSWORD above
      POSTGRES_DB: joplin
    volumes:
      - joplin_pg_data:/var/lib/postgresql/data
volumes:
  joplin_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=joplin" -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
AGPL-3.0
Category
Productivity
Replaces
Evernote, OneNote
Tech stack
Node.jsPostgreSQLReact Native

Under the hood

Database

PostgreSQL / SQLite

Language

TypeScript / Node.js

Platforms

Web · Desktop (Mac/Win/Linux) · Mobile (iOS/Android)

Key features

  • Markdown notes with optional end-to-end encryption
  • Native desktop, mobile and web apps, all synced
  • Community plugins and themes
💾 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:22300
}

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