Recipery ships as a single container image
(ghcr.io/recipery-dev/recipery:latest) with no database — deploying it is
really two independent choices: which platform runs the container, and
where recipes are stored. This section covers the platform; see
Storage for the storage backends.
Docker
A docker run or Compose file — the fastest way to try Recipery or
run it on a single machine. See Docker.
Cloudflare
Deploy the app itself as a Cloudflare Worker, backed by a native R2 binding. See Cloudflare.
Kubernetes
Example manifests for running the container in a cluster. See Kubernetes.
Which one should I use?
| Platform | Good for | Storage |
|---|---|---|
| Docker | Trying Recipery, single-machine self-hosting | Local, S3, or R2 |
| Cloudflare | Running with no server to maintain | R2 only, via a native binding |
| Kubernetes | Running alongside other self-hosted services in a cluster | S3 or R2 recommended — see the caveat on local disk |