English
Grocy Hosting
Track groceries, household supplies, chores, recipes, and everyday home inventory.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Official links
Grocy’s official links and original website
Grocy Website
More
Tech
- Docker image
- lscr.io/linuxserver/grocy:latest
- Default port
- 80
How Grocy works
Grocy records products and their quantities, storage locations, purchase dates, expiry dates, minimum stock levels, and consumption. Users can add purchases, mark items consumed, transfer stock, correct counts, and generate shopping-list entries. Recipe records can use ingredients from the same product catalogue, linking meal planning with available stock and expected consumption.
Beyond groceries, the application includes chores, tasks, batteries, equipment, and other household tracking modules. Recurring schedules surface work that is due, while history shows what was completed or changed. The system depends on accurate entries: barcode scanning and workflow shortcuts reduce typing, but Grocy cannot know what was bought, used, discarded, or moved unless a user or connected tool records it.
Key Grocy features
Grocy is flexible because modules can be used independently. A household may start with shopping lists and stock, then add recipes, chores, batteries, or equipment after the basic product catalogue is stable. Units, locations, quantities, and conversion rules need thoughtful setup to avoid confusing balances and misleading recipe calculations.
The catalogue uses Grocy’s fixed upstream first-run credentials admin / admin. They cannot be injected through the environment, so the password must be changed immediately after sign-in. The hosted plan does not include barcode hardware, companion mobile apps, retailer feeds, nutrition databases, or automatic reconciliation with physical cupboards.
Who uses Grocy
Families track pantry and freezer stock, shared flats coordinate chores and shopping, and small community kitchens record supplies and recurring maintenance. Recipe users can connect ingredient needs with on-hand quantities, while equipment owners track batteries and service intervals from the same interface.
The application should not be treated as an audited inventory, medical nutrition system, food-safety authority, or substitute for checking dates and storage conditions physically. Household records reflect user input and may become inaccurate when purchases or consumption are skipped.
Self-hosting Grocy: requirements and cost
Grocy demand is driven by products, transaction history, recipes, chores, tasks, equipment records, uploaded assets, concurrent household users, and reporting activity. The catalogue records PostgreSQL and MariaDB as Not required and persists the Grocy configuration directory. The entry plan is appropriate for ordinary household use, with data quality usually more important than raw compute.
On AvaHost, Grocy uses Plan 1 at €2. The hosted Grocy package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The first-run admin / admin credentials are fixed by the upstream image and must be replaced immediately. Barcode scanners, mobile clients, retailer integrations, nutrition services, and physical inventory verification are not included. Keep units and locations consistent, back up important records independently, and reconcile digital quantities with the actual household stock.
F.A.Q
Grocy starts at €2 on Plan 1. The mapped plan is suitable for a typical household with ordinary product, recipe, chore, task, and transaction records. User count, uploaded assets, retained history, reporting activity, and unusually large catalogues are the main reasons to inspect resource use as the installation matures.
The upstream image starts with the fixed username and password `admin` / `admin`, and the catalogue cannot replace them through environment variables. Sign in promptly and set a new password before sharing the address. Review users and permissions as well, because automated HTTPS cannot protect an installation left on publicly known first-run credentials.
A custom domain can be connected to Grocy, with automated HTTPS provided after DNS points to the hosted application. The final address can be used by household members and compatible integrations. HTTPS protects the network connection, while users remain responsible for strong credentials, accurate stock entries, and the security of any connected scanner or client.
AvaHost applies application updates automatically and includes scheduled backups, but Grocy’s inventory still reflects human or integration input. Purchases, consumption, waste, transfers, and corrections must be recorded consistently. Barcode hardware, retailer feeds, nutrition databases, and physical stock reconciliation are not part of the plan, so households should periodically compare the digital records with reality.