Wishlist — Self-Hosted, Open-Source

Wishlist application that you can share with your friends and family.

License: MIT. Built with: TypeScript, Svelte, CSS, HTML, JavaScript, Dockerfile, Shell. Source: https://github.com/cmintey/wishlist.

Features

[x] Claim items on a wishlist
[x] Check off claimed items as purchased
[x] Automatically fetch product data from URL
[x] Invite users via email (SMTP configuration required)
[x] Options for suggestions
[x] PWA Support
[x] Multiple groups
[x] Registry Mode (single list)
[x] OAuth Authentication

Installation

Then simply run `docker compose up -d`. You can now connect to your application at `http://<host>:3280`. > [!NOTE] > Set the `ORIGIN` environment variable to the url you will be connecting to, otherwise you will experience issues ### Environment Variables `ORIGIN`: The URL your users will connect to e.g. `https://wishlist.domain.com`, `http://192.168.2.10:3280`. **Note**, if this value is an IP address, then it must include the exposed port of the application `TOKEN_TIME`: The amount of time (hours) that signup and password reset tokens are valid for `DEFAULT_CURRENCY`: The global default currency (ISO-Code) to be used. Currency can still be changed on a per-item basis `MAX_IMAGE_SIZE`: Maxinum image size that can be uploaded (in bytes). Defaults to 5000000 (5MB) ### Running behind a reverse proxy It is recommended to run Wishlist behind a reverse proxy. Currently, Wishlist does not support running on a different subpath (i.e. `https://domain.com/wishlist`). #### Nginx / Synology NAS There is a [known issue](https://github.com/cmintey/wishlist/issues/170) when running behind Nginx or Synology NAS (which uses Nginx under the hood) proxies. It is recommended to set the following properties in your Nginx configuration:

Why self-host Wishlist

Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.

What hardware do you need

Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through Wishlist. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.

Where to go from here

Last verified: 2026-04-22