How to order Wger?

Deploy Wger as a fully managed service starting at €9/month. Get automated backups, SSL, updates, monitoring, and human support, all included.

DANIAN runs Wger as a fully managed service: installation, updates, backups, monitoring and security are handled for you.

See the Wger hosting page for plans, pricing and a free trial.

1. Login at: https://portal.danian.co

2. Manage Apps - Add an App

3. Select: Wger

4. Select service Region

This is the datacenter location where your App will be located.

5. Select the App Address (URL) - Select 1 of the 2 options:

A. Use a free URL provided by DANIAN

B. Use my own Domain/Subdomain. Then enter the URL. Later an automated email will be send to you with additional info.

6. Click: Send

7. You will be notified via email as soon as your App is activated.

8. To access the App credentials:

https://portal.danian.co - Manage Apps - My Apps - Click on the App
There you will find:
A. Account related info: Email, Username
B. App related info: Order Date
C. App info: App name, Plan, Disk, Region, Public IP Address, Charge
D. App Login: URL, Username and/or Email, Password & Useful info
E. Status: Delivered or Pending
F. Total Cost per month

About Wger

wger is a Django application for tracking workouts, nutrition and body measurements, published under AGPL-3.0-or-later. It carries a community-maintained exercise database, a nutrition module fed by Open Food Facts data, a documented REST API, and mobile clients for Android and iOS.

The project is led by Roland Geider and maintained by the wger team rather than a company. The application code is AGPL-3.0-or-later and the documentation is CC-BY-SA. The exercise database is a wiki: users write the descriptions, contribute the images and videos, and translate them through Weblate, and instances pull the result from the project's reference server. Ingredient data comes from Open Food Facts under the Open Database License, which is why barcode scanning works out of the box rather than through a paid nutrition API.

The install footprint is larger than a single container suggests. A working instance wants Postgres, a Redis cache, at least one Celery worker for the scheduled sync tasks, and gunicorn behind a reverse proxy. The full ingredient dataset takes roughly a gigabyte of database space on its own, which is why the upstream image ships with exercises but no ingredients. The Android and iOS apps are thin clients against the REST API: you point them at your own server address, and they move version by version with the server behind them.