Self-Host Memos: Lightweight Notes and Microblog 2026

TL;DR

Memos (MIT, ~33K GitHub stars, Go) is a privacy-first, lightweight note-taking app that feels like a personal Twitter feed. Jot down thoughts, code snippets, links, and ideas in Markdown — everything is timestamped and appears in a scrollable feed. Tags for organization, search for retrieval, REST API for automation. Standard Notes charges $90/year for premium; Apple Notes locks you into iCloud. Memos runs on your server with full data ownership.

Key Takeaways

Memos: MIT, ~33K stars, Go — fast, lightweight notes with a feed-like UI
Markdown: Full Markdown support with code blocks, links, images, and checklists
Tags: Organize with #tags inline — no folders, no hierarchy, just tags
Timeline feed: Scrollable chronological feed like a personal microblog
REST API: Full CRUD API for integrations — Telegram bot, iOS Shortcuts, CLI
Multi-user: Invite others, share memos publicly, or keep everything private
Tiny footprint: ~30MB RAM, SQLite — runs on the smallest server

Memos vs Apple Notes vs Notion vs Standard Notes

Feature	Memos	Apple Notes	Notion	Standard Notes
Price	Free (self-host)	Free (iCloud)	$8/mo (Plus)	$90/yr
Data ownership	Full	Apple	Notion	E2E encrypted
Markdown	Yes	No	Partial	Yes
Feed/timeline	Yes	No	No	No
Tags	Inline #tags	Folders	Pages	Tags
API	REST	No	REST	No
Multi-user	Yes	Via iCloud sharing	Yes	No
Offline	PWA	Native	Limited	Native
Self-hosted	Yes	No	No	Yes

Part 1: Docker Setup

# docker-compose.yml
services:
  memos:
    image: neosmemo/memos:stable
    container_name: memos
    restart: unless-stopped
    ports:
      - "5230:5230"
    volumes:
      - memos_data:/var/opt/memos
    environment:
      # Memos uses SQLite by default — zero config needed
      # Optional: use PostgreSQL instead:
      # MEMOS_DRIVER: postgres
      # MEMOS_DSN: "postgresql://memos:password@db:5432/memos?sslmode=disable"
      MEMOS_MODE: prod

volumes:
  memos_data:

docker compose up -d

Visit http://your-server:5230 → create your admin account.

Part 2: HTTPS with Caddy

memos.yourdomain.com {
    reverse_proxy localhost:5230
}

Part 3: Writing Memos

Quick capture

The text area at the top of the feed is always ready. Type a thought and hit Save:

Just discovered that Docker Compose v2.27 supports
`include` for composing multiple files natively. 
No more `-f file1.yml -f file2.yml`!

#docker #til

Markdown features

# Headers
**Bold** and *italic*

- Bullet lists
- [x] Checklists
- [ ] Todo items

`inline code` and code blocks:

\`\`\`python
print("Hello from Memos!")
\`\`\`

> Blockquotes for excerpts

[Links](https://example.com)

![Images can be uploaded or pasted](image.png)

Pinned memos

Pin important memos to the top of your feed:

Click the ⋯ menu → Pin
Pinned memos always appear first

Part 4: Organization

All tags appear in the left sidebar. Click a tag to filter your feed.

Nested tags work with /:

#work/project-a
#work/project-b
#personal/reading
#personal/ideas

Search

Full-text search across all memos:

kubernetes          — keyword search
#docker             — filter by tag
from:2026-01-01     — date filter
has:link            — memos containing links
has:code            — memos with code blocks

Filters

Save common filters for quick access:

All memos — everything
Tags — filter by specific tag
Date range — this week, this month, custom

Visibility levels

Level	Who can see
Private	Only you
Protected	Logged-in users on your instance
Public	Anyone with the URL

Set visibility per memo:

Default: Private
Click the 🔒 icon → switch to Protected or Public

Click ⋯ → Share
Copy the direct link: https://memos.yourdomain.com/m/abc123
Public memos are accessible without login

RSS feed

Public memos are available as an RSS feed:

https://memos.yourdomain.com/u/yourname/rss.xml

Subscribe from any RSS reader to follow someone's public notes.

Part 6: REST API

# Get your access token:
# Settings → Access Tokens → Create

TOKEN="your-access-token"
BASE="https://memos.yourdomain.com"

# Create a memo:
curl -X POST "$BASE/api/v1/memos" \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Automated memo from a script! #automation",
    "visibility": "PRIVATE"
  }'

# List memos:
curl "$BASE/api/v1/memos" \
  -H "Authorization: Bearer $TOKEN" | jq '.memos[].content'

# Search memos:
curl "$BASE/api/v1/memos?filter=content.contains(\"kubernetes\")" \
  -H "Authorization: Bearer $TOKEN"

# Delete a memo:
curl -X DELETE "$BASE/api/v1/memos/MEMO_NAME" \
  -H "Authorization: Bearer $TOKEN"

Part 7: Integrations

Telegram bot

Capture memos from Telegram:

#!/usr/bin/env python3
# telegram-to-memos.py
import os
import requests
from telegram import Update
from telegram.ext import ApplicationBuilder, MessageHandler, filters

MEMOS_URL = "https://memos.yourdomain.com"
MEMOS_TOKEN = os.environ["MEMOS_TOKEN"]
TELEGRAM_TOKEN = os.environ["TELEGRAM_TOKEN"]

async def save_memo(update: Update, context):
    text = update.message.text
    requests.post(
        f"{MEMOS_URL}/api/v1/memos",
        headers={"Authorization": f"Bearer {MEMOS_TOKEN}"},
        json={"content": text, "visibility": "PRIVATE"}
    )
    await update.message.reply_text("✅ Saved to Memos!")

app = ApplicationBuilder().token(TELEGRAM_TOKEN).build()
app.add_handler(MessageHandler(filters.TEXT, save_memo))
app.run_polling()

iOS Shortcuts

Shortcuts → New → Ask for Input (text)
Get Contents of URL:
- URL: https://memos.yourdomain.com/api/v1/memos
- Method: POST
- Headers: Authorization: Bearer YOUR_TOKEN
- Body: {"content": "Shortcut Input", "visibility": "PRIVATE"}
Show Result: "Saved!"
Add to Home Screen or Share Sheet

CLI quick-capture

# Add to ~/.bashrc or ~/.zshrc:
memo() {
  curl -s -X POST "https://memos.yourdomain.com/api/v1/memos" \
    -H "Authorization: Bearer $MEMOS_TOKEN" \
    -H "Content-Type: application/json" \
    -d "{\"content\": \"$*\", \"visibility\": \"PRIVATE\"}" > /dev/null
  echo "✅ Saved"
}

# Usage:
memo "Just found a great article on #rust error handling"
memo "TODO: update the CI pipeline #work"

Part 8: Multi-User Setup

Create additional users

Settings → Members → + Add Member:
  Username: alice
  Role: User / Admin

Roles

Role	Capabilities
Host (Admin)	Full access, manage users, system settings
Admin	Create/edit/delete own memos, view protected memos
User	Create/edit/delete own memos, view protected memos

Maintenance

# Update:
docker compose pull
docker compose up -d

# Backup (SQLite):
docker cp memos:/var/opt/memos/memos_prod.db \
  memos-backup-$(date +%Y%m%d).db

# Or full data directory (includes uploaded files):
tar -czf memos-data-$(date +%Y%m%d).tar.gz \
  $(docker volume inspect memos_memos_data --format '{{.Mountpoint}}')

# Logs:
docker compose logs -f memos

Why Self-Host Memos?

The case for self-hosting Memos comes down to three practical factors: data ownership, cost at scale, and operational control.

Data ownership is the fundamental argument. When you use a SaaS version of any tool, your data lives on someone else's infrastructure subject to their terms of service, their security practices, and their business continuity. If the vendor raises prices, gets acquired, changes API limits, or shuts down, you're left scrambling. Self-hosting Memos means your data and configuration stay on infrastructure you control — whether that's a VPS, a bare metal server, or a home lab.

Cost at scale matters once you move beyond individual use. Most SaaS equivalents charge per user or per data volume. A self-hosted instance on a $10-20/month VPS typically costs less than per-user SaaS pricing for teams of five or more — and the cost doesn't scale linearly with usage. One well-configured server handles dozens of users for a flat monthly fee.

Operational control is the third factor. The Docker Compose configuration above exposes every setting that commercial equivalents often hide behind enterprise plans: custom networking, environment variables, storage backends, and authentication integrations. You decide when to update, how to configure backups, and what access controls to apply.

The honest tradeoff: you're responsible for updates, backups, and availability. For teams running any production workloads, this is familiar territory. For individuals, the learning curve is real but the tooling (Docker, Caddy, automated backups) is well-documented and widely supported.

Server Requirements and Sizing

Before deploying Memos, assess your server capacity against expected workload.

Minimum viable setup: A 1 vCPU, 1GB RAM VPS with 20GB SSD is sufficient for personal use or small teams. Most consumer VPS providers — Hetzner, DigitalOcean, Linode, Vultr — offer machines in this range for $5-10/month. Hetzner offers excellent price-to-performance for European and US regions.

Recommended production setup: 2 vCPUs with 4GB RAM and 40GB SSD handles most medium deployments without resource contention. This gives Memos headroom for background tasks, caching, and concurrent users while leaving capacity for other services on the same host.

Storage planning: The Docker volumes in this docker-compose.yml store all persistent Memos data. Estimate your storage growth rate early — for data-intensive tools, budget for 3-5x your initial estimate. Hetzner Cloud and Vultr both support online volume resizing without stopping your instance.

Operating system: Any modern 64-bit Linux distribution works. Ubuntu 22.04 LTS and Debian 12 are the most commonly tested configurations. Ensure Docker Engine 24.0+ and Docker Compose v2 are installed — verify with docker --version and docker compose version. Avoid Docker Desktop on production Linux servers; it adds virtualization overhead and behaves differently from Docker Engine in ways that cause subtle networking issues.

Network: Only ports 80 and 443 need to be publicly accessible when running behind a reverse proxy. Internal service ports should be bound to localhost only. A minimal UFW firewall that blocks all inbound traffic except SSH, HTTP, and HTTPS is the single most effective security measure for a self-hosted server.

Backup and Disaster Recovery

Running Memos without a tested backup strategy is an unacceptable availability risk. Docker volumes are not automatically backed up — if you delete a volume or the host fails, data is gone with no recovery path.

What to back up: The named Docker volumes containing Memos's data (database files, user uploads, application state), your docker-compose.yml and any customized configuration files, and .env files containing secrets.

Backup approach: For simple setups, stop the container, archive the volume contents, then restart. For production environments where stopping causes disruption, use filesystem snapshots or database dump commands (PostgreSQL pg_dump, SQLite .backup, MySQL mysqldump) that produce consistent backups without downtime.

For a complete automated backup workflow that ships snapshots to S3-compatible object storage, see the Restic + Rclone backup guide. Restic handles deduplication and encryption; Rclone handles multi-destination uploads. The same setup works for any Docker volume.

Backup cadence: Daily backups to remote storage are a reasonable baseline for actively used tools. Use a 30-day retention window minimum — long enough to recover from mistakes discovered weeks later. For critical data, extend to 90 days and use a secondary destination.

Restore testing: A backup that has never been restored is a backup you cannot trust. Once a month, restore your Memos backup to a separate Docker Compose stack on different ports and verify the data is intact. This catches silent backup failures, script errors, and volume permission issues before they matter in a real recovery.

Security Hardening

Self-hosting means you are responsible for Memos's security posture. The Docker Compose setup provides a functional base; production deployments need additional hardening.

Always use a reverse proxy: Never expose Memos's internal port directly to the internet. The docker-compose.yml binds to localhost; Caddy or Nginx provides HTTPS termination. Direct HTTP access transmits credentials in plaintext. A reverse proxy also centralizes TLS management, rate limiting, and access logging.

Strong credentials: Change default passwords immediately after first login. For secrets in docker-compose environment variables, generate random values with openssl rand -base64 32 rather than reusing existing passwords.

Firewall configuration:

ufw default deny incoming
ufw allow 22/tcp
ufw allow 80/tcp
ufw allow 443/tcp
ufw enable

Internal service ports (databases, admin panels, internal APIs) should only be reachable from localhost or the Docker network, never directly from the internet.

Network isolation: Docker Compose named networks keep Memos's services isolated from other containers on the same host. Database containers should not share networks with containers that don't need direct database access.

VPN access for sensitive services: For internal-only tools, restricting access to a VPN adds a strong second layer. Headscale is an open source Tailscale control server that puts your self-hosted stack behind a WireGuard mesh, eliminating public internet exposure for internal tools.

Update discipline: Subscribe to Memos's GitHub releases page to receive security advisory notifications. Schedule a monthly maintenance window to pull updated images. Running outdated container images is the most common cause of self-hosted service compromises.

Troubleshooting Common Issues

Container exits immediately or won't start

Check logs first — they almost always explain the failure:

docker compose logs -f memos

Common causes: a missing required environment variable, a port already in use, or a volume permission error. Port conflicts appear as bind: address already in use. Find the conflicting process with ss -tlpn | grep PORT and either stop it or change Memos's port mapping in docker-compose.yml.

Cannot reach the web interface

Work through this checklist:

Confirm the container is running: docker compose ps
Test locally on the server: curl -I http://localhost:PORT
If local access works but external doesn't, check your firewall: ufw status
If using a reverse proxy, verify it's running and the config is valid: caddy validate --config /etc/caddy/Caddyfile

Permission errors on volume mounts

Some containers run as a non-root user. If the Docker volume is owned by root, the container process cannot write to it. Find the volume's host path with docker volume inspect VOLUME_NAME, check the tool's documentation for its expected UID, and apply correct ownership:

chown -R 1000:1000 /var/lib/docker/volumes/your_volume/_data

High resource usage over time

Memory or CPU growing continuously usually indicates unconfigured log rotation, an unbound cache, or accumulated data needing pruning. Check current usage with docker stats memos. Add resource limits in docker-compose.yml to prevent one container from starving others. For ongoing visibility into resource trends, deploy Prometheus + Grafana or Netdata.

Data disappears after container restart

Data stored in the container's writable layer — rather than a named volume — is lost when the container is removed or recreated. This happens when the volume mount path in docker-compose.yml doesn't match where the application writes data. Verify mount paths against the tool's documentation and correct the mapping. Named volumes persist across container removal; only docker compose down -v deletes them.

Keeping Memos Updated

Memos follows a regular release cadence. Staying current matters for security patches and compatibility. The update process with Docker Compose is straightforward:

docker compose pull          # Download updated images
docker compose up -d         # Restart with new images
docker image prune -f        # Remove old image layers (optional)

Read the changelog before major version updates. Some releases include database migrations or breaking configuration changes. For major version bumps, test in a staging environment first — run a copy of the service on different ports with the same volume data to validate the migration before touching production.

Version pinning: For stability, pin to a specific image tag in docker-compose.yml instead of latest. Update deliberately after reviewing the changelog. This trades automatic patch delivery for predictable behavior — the right call for business-critical services.

Post-update verification: After updating, confirm Memos is functioning correctly. Most services expose a /health endpoint that returns HTTP 200 — curl it from the server or monitor it with your uptime tool.

See all open source productivity tools at OSSAlt.com/categories/productivity.