Deploy and Host

This template deploys Grocy 4.7.1 — the self-hosted household ERP (grocery stock, shopping list, recipes, chores, batteries, tasks) — as a single container on Railway with one persistent volume and zero required deploy-form prompts.

First login is admin / admin. Change the password immediately (top-right user menu, then Users, then admin, then edit) — your instance is on the public internet, so this is not optional.

After deploying, open your Railway domain, sign in with those default credentials, and Grocy walks you through first use: add products, track stock, plan meals.

One-click deploy button:

Grocy is a PHP + SQLite application that runs entirely in one container — no external database service, no sidecars. This template serves the official, digest-pinned LinuxServer.io image of Grocy 4.7.1 (unchanged upstream), fronts it with Railway's TLS edge pointed at the container's fixed nginx port 80, and keeps every byte of state in the /config volume.

About Hosting

Hosting Grocy yourself means your household's data — stock levels, shopping lists, recipes, chore schedules — lives in a single SQLite file on your volume. Nothing leaves your instance; there is no cloud account, no telemetry, no vendor lock-in. The template provisions:

One service — the digest-pinned linuxserver/grocy image (Grocy 4.7.1), unmodified upstream (Railway terminates TLS at the edge and forwards to the container's port 80).
One volume mounted at /config — the SQLite database, config.php, plugins, and caches all live there, so everything persists across deploys and restarts.
Zero required variables — Grocy works out of the box; optional GROCY_* overrides can be added later in the Variables tab.

Rough sizing: Grocy idles under ~100 MB of RAM; a household database with thousands of stock entries is a few MB. The default volume size is far more than a household ever needs. First boot runs Grocy's database migration automatically when you first open the site.

Why Deploy

Instant household ERP: deploy, log in with admin / admin, change the password — you are tracking stock in under five minutes.
Zero-prompt deploy: no deploy-time questions, no variables to pre-fill, no database to attach; the volume is provisioned with the service in one click.
Official image, pinned: the Dockerfile pins linuxserver/grocy by digest, so every deploy of this template is bit-identical Grocy 4.7.1 — no surprise tag drift, no wrapper scripts touching the app.
Everything persists: stock, users, settings, and uploaded pictures live on the /config volume; restarts and redeploys keep your data.
Your data, portable: the whole state is one SQLite file — copy it off the volume with any backup tool and you have a complete household archive.

Common Use Cases

Grocery stock management — what is in the pantry, what expires when, what to buy (Grocy even prints barcodes and handles a USB barcode scanner).
Shared shopping list — the whole household edits one live list from phones; items flow in from stock shortfalls and recipes.
Meal planning — recipes, per-portion costs, and a calendar that subtracts ingredients from stock when you cook.
Chores and chores rotation — who does what, when it was last done, and the next due date.
Small-inventory tracking — batteries, tools, spare parts, or a freezer inventory with location-aware quantity tracking.

Dependencies for

Deployment Dependencies

Railway account — the template provisions one service plus one volume; no external database or other services are needed.
No required variables — nothing must be set at deploy time. Optional later: TZ (timezone), PUID/PGID (runtime UID/GID), GROCY_CURRENCY, GROCY_AUTH_CLASS for LDAP sign-in, and GROCY_FEATURE_FLAG_* toggles to hide unused modules; see the repository README.
A browser for everyday use — Grocy's UI is fully responsive and works from phones. The API and barcode integrations are included in the image.
Upstream software: Grocy 4.7.1 (MIT) served by the official linuxserver/grocy container image (GPLv3); licenses are listed by their upstream projects.