Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
A personal recipe keeper, meal planner and shopping-list organizer with web, iOS and Android apps. It can import recipes from URLs, images, PDFs and text (self-hosted, those imports need your own AI provider key), scales and converts units, tracks nutrition, works offline and shares lists and plans with family. The selfhost stack runs a Node API, a static frontend, nginx, Pushpin, PostgreSQL and Valkey. The main project is AGPL-3.0 for non-commercial use with commercial use by request, and the selfhost images are for personal, private, non-commercial use only.
Runs on a VPS from $6/mo (Kamatera 2GB, 2 GB RAM) · prices checked Nov 2026
Fits home hardware (449 MB measured idle, RAM only): Raspberry Pi 4 (4 GB) (arm64 untested), Raspberry Pi 5 (8 GB) (arm64 untested), Repurposed laptop (8 GB), Intel N100 mini PC (16 GB), AMD Ryzen mini PC (32 GB).
Pick RecipeSage when you want a personal recipe keeper with meal planning, shared shopping lists and offline use, and you are running it for yourself or your household. It scales and converts units, tracks nutrition and has web, iOS and Android apps, and it can import recipes from URLs, images, PDFs and text once you add your own AI provider key. The licensing is restricted: the main README says RecipeSage is AGPL-3.0 for non-commercial use only and commercial use needs a licence on request, and the selfhost repository's `LICENSE.md` limits the repository, images, code and branding to personal, private, non-commercial use, so we do not list it as plain open source. Our snippet follows the `recipesage-selfhost` Compose file (config 2026-10-29) with the API and static images moved from `v4.1.0` to `v4.1.2` (published 2026-11-02), PostgreSQL pinned to 16.11, Valkey to 8.1.4, and the database password and `GRIP_KEY` generated. Upstream's file is written for 4.1.0 and asks that values below its marker stay unchanged, so these image bumps and pins go beyond what it supports; `v4.1.1` and `v4.1.2` are small releases. No RAM minimum is published, so our 1024 MB floor is an estimate; the Compose file caps the Node heap at 400 MB. In the catalog, Mealie and Tandoor are recipe managers under AGPL-3.0 (Tandoor with a Commons Clause) and KitchenOwl is a grocery list with recipes; RecipeSage is the one whose terms limit use to non-commercial, so check that fits before choosing it.
Paid link — we earn a commission if you shop through it.
Run these commands on your server:
# RecipeSage — recipe keeper, meal planner and shopping lists — adapted from recipesage-selfhost docker-compose.yml (config 2026-10-29), api and static images bumped to v4.1.2
# Changed from upstream: images pinned (postgres 16.11, valkey 8.1.4), database password and GRIP_KEY generated into .env, API_PUBLIC_BASE_URL set to http://localhost:7270/api (edit it to the address your browser uses)
mkdir recipesage && cd recipesage
echo "PG_PASSWORD=$(openssl rand -hex 16)" > .env
echo "GRIP_KEY=$(openssl rand -hex 16)" >> .env
cat > docker-compose.yml <<'EOF'
x-common-env: &common-env
API_PUBLIC_BASE_URL: http://localhost:7270/api
GRIP_KEY: ${GRIP_KEY}
POSTGRES_DB: recipesage_selfhost
POSTGRES_USER: recipesage_selfhost
POSTGRES_PASSWORD: ${PG_PASSWORD}
DATABASE_URL: postgresql://recipesage_selfhost:${PG_PASSWORD}@postgres:5432/recipesage_selfhost
GROCERY_CATEGORIZER_URL: https://grocery-categorizer.recipesage.com/
AI_PROVIDER: "openrouter"
AI_API_KEY: ""
AI_API_BASE_URL: ""
AI_MODEL_WEBPAGE: google/gemini-2.5-flash-lite
AI_MODEL_TEXT: google/gemini-2.5-flash-lite
AI_MODEL_OCR: google/gemini-2.5-flash
AI_MODEL_DOCUMENT: google/gemini-2.5-flash
AI_MODEL_MODERATION: google/gemini-2.5-flash
AI_MODEL_VISION: anthropic/claude-sonnet-4.6
AI_MODEL_NUTRITION: google/gemini-2.5-flash-lite
AI_MODEL_ASSISTANT: anthropic/claude-sonnet-4.6
AI_MODEL_ASSISTANT_LOW: google/gemini-2.5-flash
SCRAPFLY_API_KEY: ""
services:
proxy:
container_name: recipesage_proxy
image: julianpoy/recipesage-selfhost-proxy:2026-08-16
ports:
- 7270:80
depends_on:
- static
- api
- pushpin
restart: unless-stopped
static:
container_name: recipesage_static
image: julianpoy/recipesage-selfhost:static-v4.1.2
restart: unless-stopped
api:
container_name: recipesage_api
image: julianpoy/recipesage-selfhost:api-v4.1.2
depends_on:
postgres:
condition: service_healthy
pushpin:
condition: service_started
valkey:
condition: service_started
command: ./scripts/selfhost-startup.sh
environment:
<<: *common-env
ENVIRONMENT: selfhost
NODE_ENV: selfhost
NODE_OPTIONS: "--max-old-space-size=400"
MALLOC_ARENA_MAX: "2"
FILESYSTEM_STORAGE_PATH: /rs-media
STORAGE_TYPE: filesystem
VERBOSE: "false"
VERSION: selfhost
POSTGRES_HOST: postgres
POSTGRES_PORT: "5432"
POSTGRES_SSL: "false"
POSTGRES_LOGGING: "false"
DATABASE_SSL: "false"
GRIP_URL: http://pushpin:5561/
JOB_QUEUE_REDIS_HOST: valkey
STRIPE_SK: ""
GCM_KEYPAIR: ""
SENTRY_DSN: ""
STRIPE_WEBHOOK_SECRET: ""
volumes:
- apimedia:/rs-media
restart: unless-stopped
pushpin:
container_name: recipesage_pushpin
image: julianpoy/pushpin:2023-09-17
entrypoint: /bin/sh -c
command:
[
'sed -i "s/sig_key=changeme/sig_key=$$GRIP_KEY/" /etc/pushpin/pushpin.conf && echo "* $${TARGET},over_http" > /etc/pushpin/routes && pushpin --merge-output',
]
environment:
<<: *common-env
TARGET: api:3000
restart: unless-stopped
postgres:
container_name: recipesage_postgres
image: postgres:16.11
environment:
<<: *common-env
volumes:
- postgresdata:/var/lib/postgresql/data
restart: unless-stopped
healthcheck:
test: ["CMD", "pg_isready", "-d", "recipesage_selfhost", "-U", "recipesage_selfhost"]
interval: 5s
timeout: 5s
retries: 5
start_period: 10s
valkey:
restart: unless-stopped
image: valkey/valkey:8.1.4
volumes:
apimedia:
driver: local
postgresdata:
driver: local
EOF
docker compose up -d
timeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:7270/api/healthz; do sleep 3; done'
# → http://SERVER_IP:7270 (register the first account; the web app is served under /app/ and registration is open until you set DISABLE_REGISTRATION=true)RecipeSage's README, the selfhost README and LICENSE.md, and the Compose file flag these before you rely on it:
RecipeSage used 449 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 1024 MB.
The RecipeSage install snippet is marked verified on Ubuntu 26.04 (Nov 2026).