PinePods

See the full feature catalog in the docs.

Screenshots :camera:

Try it out! :zap:

A public demo instance lives at try.pinepods.online — make an account and take a look before you self-host. It's for evaluation only; accounts there are wiped periodically, so run your own server for real use.

Quick Start :rocket:

The fastest way to run PinePods is Docker Compose with PostgreSQL. Create a docker-compose.yml:

services:
  db:
    container_name: db
    image: postgres:18
    environment:
      POSTGRES_DB: pinepods_database
      POSTGRES_USER: postgres
      POSTGRES_PASSWORD: myS3curepass
      PGDATA: /var/lib/pgdata/pgdata
    volumes:
      - /home/user/pinepods/pgdata:/var/lib/pgdata
    restart: always

  valkey:
    image: valkey/valkey:8-alpine
    restart: always

  pinepods:
    image: madeofpendletonwool/pinepods:latest
    ports:
      - "8040:8040"
    environment:
      # Basic server info
      SEARCH_API_URL: 'https://search.pinepods.online/api/search'
      PEOPLE_API_URL: 'https://people.pinepods.online'
      HOSTNAME: 'http://localhost:8040'
      # Database
      DB_TYPE: postgresql
      DB_HOST: db
      DB_PORT: 5432
      DB_USER: postgres
      DB_PASSWORD: myS3curepass
      DB_NAME: pinepods_database
      # Valkey cache
      VALKEY_HOST: valkey
      VALKEY_PORT: 6379
      DEBUG_MODE: false
      # Run as your host user so downloads stay accessible (optional)
      PUID: ${UID:-911}
      PGID: ${GID:-911}
      # Local timezone (optional, used for logs)
      TZ: "America/New_York"
    volumes:
      - /home/user/pinepods/downloads:/opt/pinepods/downloads
      - /home/user/pinepods/backups:/opt/pinepods/backups
    restart: always
    depends_on:
      - db
      - valkey

Then start it:

sudo docker compose up -d

Open http://localhost:8040 and you'll be prompted to create your first admin account. That's it — you're up.

:information_source: On PostgreSQL 18 / upgrading from 17. New installs default to postgres:18 and need no special steps. Two things to know when moving an existing install to 18:

• Data isn't auto-migrated across major versions. postgres:18 won't start against a data directory created by 17 (FATAL: database files are incompatible with server). Your data is safe — run deployment/docker/upgrade-postgres.sh (takes a backup, then upgrades in place) or follow the Upgrading PostgreSQL guide. Back up first — the upgrade is one-way.
• The postgres:18 image moved its data dir and VOLUME. Bind-mounting to the old /var/lib/postgresql/data can fail on some Linux/overlay2 hosts with change mount propagation through procfd ... no such file or directory. The compose above avoids this by mounting at /var/lib/pgdata, outside the image's VOLUME; use that same pattern when you upgrade. See docker-library/postgres#1363.

Need more? Helm/Kubernetes, MySQL/MariaDB, admin bootstrap vars, the self-hosted search API, timezone tuning, PUID/PGID, and OIDC are all covered in the docs:

• :whale: Full server install guide
• :anchor: Helm chart — helm repo add pinepods http://helm.pinepods.online
• :mag: Self-hosting the search API
• :closed_lock_with_key: OIDC / SSO setup

Clients

Run the server, then connect any client by pointing it at your server URL and signing in. The web client is served by the server itself — the rest are optional native apps.