Never run out of your medications again.
A medication tracking and planning app with stock monitoring, intake schedules, and reminder notifications.
This app was 100% coded with Claude Opus 4.6 and GPT-5.3 Codex. Use at your own risk.
Your health is your responsibility. This app may contain bugs. Follow your doctor's instructions closely, keep track of your medication supply, and plan ahead for reordering.
Think of this app as a helpful tool, but make all health decisions independently!
Screenshots
- Optional multi-source lookup inside the medication editor on desktop and mobile, prioritizing
RxNormandopenFDAbeforeEMA, including package-size suggestions when the source exposes them - Explicit review-and-apply flow with low-risk suggestions only
- Additional lookup results can be revealed on demand instead of being hard-cut at the initial small result set
- Honest incomplete-coverage messaging with source labels; manual entry always remains available
- Track exact stock with package profiles (blister, bottle, tube, liquid container)
- Display remaining days of supply
- Automatic calculation based on intake schedule
- Manual stock correction supports profile-specific stock semantics (sealed units + loose stock for blister, amount-based stock for bottle/tube/liquid)
- One-click refill with pack or loose pill options
- Complete refill history per medication
- Automatic stock updates after each refill
- Daily, weekly, or custom intervals per medication
- Independent schedules for each medication
- Optional timeline filters for dashboard and shared schedule views
- Notifications before stock runs out
- Configurable warning thresholds
- Intake reminders via push notifications
- Calculate medication demand for a trip or date range with package-aware units
- Plan ahead for vacations, business trips, or hospital stays
- Send demand reports via email or push notification
- Generate medication reports as PDF, Markdown, or plain text
- Include intake history, refill history, and prescription details
- Manage medications for multiple people
- Share schedules via link. Recipients can mark doses as taken, you see it live
- Optionally embed the medication overview directly on shared links via a settings toggle
- Export all your data (medications, dose history, settings) as JSON
- Import previously exported data with automatic ID remapping
- Choose whether to include sensitive data in exports
- Email via SMTP
- Push notifications via ntfy, Pushover, Gotify, Telegram, Discord & more (Shoutrrr)
- Supports both stock warnings and intake reminders
- Fully self-hosted
- SSO via OIDC (Authelia, Authentik, Pocket ID, Keycloak)
- Non-root containers
- Dark mode included π
The easiest way to deploy MedAssist-ng is with Docker Compose:
git clone https://github.com/DanielVolz/medassist-ng.git
cd medassist-ng
cp .env.example .env
docker compose -p medassist-ng up -dOpen http://localhost:4174 and start tracking your medications.
All configuration is done via environment variables in .env. Copy .env.example to get started.
| Variable | Default | Description |
|---|---|---|
PUID |
1000 |
User ID for container file permissions |
PGID |
1000 |
Group ID for container file permissions |
PORT |
3000 |
Backend API port |
CORS_ORIGINS |
http://localhost:4174 |
Allowed origins for CORS |
LOG_LEVEL |
info |
Log verbosity (debug, info, warn, error, silent). At info (default), high-frequency polling endpoints are suppressed. Set debug to see all requests. |
OPENAPI_DOCS_ENABLED |
auto |
Enables API docs in non-production by default. Set explicitly to true/false to override. |
TZ |
Europe/Berlin |
Server default timezone for scheduled reminders (can be overridden per user in Settings) |
Recommended values for API docs by environment:
| Environment | Recommendation |
|---|---|
| Development | OPENAPI_DOCS_ENABLED=true |
| Staging/Test | OPENAPI_DOCS_ENABLED=true |
| Production | leave it unset, or set OPENAPI_DOCS_ENABLED=false |
Notes:
- If
OPENAPI_DOCS_ENABLEDis not set, docs are enabled outside production and disabled in production. - If
OPENAPI_DOCS_ENABLED=true, docs are available on/docsand/docs/json. - If
OPENAPI_DOCS_ENABLED=false, only the docs are disabled. The API still works normally.
| Variable | Default | Description |
|---|---|---|
AUTH_ENABLED |
false |
Enable user authentication |
REGISTRATION_ENABLED |
false |
Allow new user registrations |
JWT_SECRET |
β | Access token signing key (required if auth enabled) |
REFRESH_SECRET |
β | Refresh token signing key (required if auth enabled) |
COOKIE_SECRET |
β | Cookie signing key (required if auth enabled) |
ACCESS_TOKEN_TTL_MINUTES |
15 |
Access token lifetime |
REFRESH_TOKEN_TTL_DAYS |
7 |
Refresh token lifetime |
Generate secrets with: openssl rand -hex 32
When AUTH_ENABLED=true, you can create personal API keys and call protected endpoints with:
Authorization: Bearer ma_...Available scopes:
read: read-only access (GET,HEAD,OPTIONS)write: read + write access
Essential notes:
- Create keys in the app when authentication is enabled.
- The token is shown only once after creation.
- Creating a new key automatically deactivates previously active keys for the same user.
- API keys are stored hashed in the database.
Example usage:
curl http://localhost:3000/settings \
-H "Authorization: Bearer ma_..."API reference:
- Interactive docs:
/docs - OpenAPI JSON:
/docs/json - With the bundled frontend ingress, these paths work on the normal app URL as well, for example
http://localhost:4174/docswhen docs are enabled. - Key management endpoints for authenticated users:
GET /auth/api-keysPOST /auth/api-keysDELETE /auth/api-keys/:id
| Variable | Default | Description |
|---|---|---|
OIDC_ENABLED |
false |
Enable OIDC authentication |
OIDC_ISSUER_URL |
β | OIDC provider URL |
OIDC_CLIENT_ID |
β | Client ID from OIDC provider |
OIDC_CLIENT_SECRET |
β | Client secret from OIDC provider |
OIDC_REDIRECT_URI |
β | Full callback URL (e.g., https://your-domain.com/api/auth/oidc/callback) |
OIDC_SCOPES |
openid profile email |
Scopes to request |
OIDC_USERNAME_CLAIM |
preferred_username |
Claim for username |
OIDC_AUTO_CREATE_USERS |
true |
Auto-create users on first SSO login |
OIDC_PROVIDER_NAME |
SSO |
Name shown on login button |
| Variable | Default | Description |
|---|---|---|
SMTP_HOST |
β | SMTP server hostname |
SMTP_PORT |
587 |
SMTP server port |
SMTP_USER |
β | SMTP username |
SMTP_PASS |
β | SMTP password |
SMTP_TOKEN |
β | OAuth2/App token (takes precedence over password) |
SMTP_FROM |
β | Sender email address |
SMTP_SECURE |
false |
Use TLS |
| Variable | Default | Description |
|---|---|---|
REMINDER_DAYS_BEFORE |
7 |
Days before stock runs out to send reminder |
REMINDER_HOUR |
6 |
Hour to send daily reminders (24h format) |
REMINDER_MINUTES_BEFORE |
15 |
Minutes before intake to send reminder |
EXPIRY_WARNING_DAYS |
30 |
Days before expiry to show warning |
Intake reminder timing uses IANA timezones. The server uses TZ as default, and each user can set an override in Settings. If no user timezone is set, reminders continue using the server default.
MedAssist uses Shoutrrr for push notifications, supporting many services with a single URL format.
Implemented URL schemes in MedAssist: ntfy://, discord://, pushover://, gotify://, telegram://, plus direct https:// webhooks.
This covers common providers like ntfy, Discord, Pushover, Gotify, Telegram, Slack webhooks, and many others via webhook URLs.
Configure push notifications in Settings β Push, or set defaults via environment variables:
| Variable | Default | Description |
|---|---|---|
DEFAULT_SHOUTRRR_ENABLED |
false |
Enable push notifications by default |
DEFAULT_SHOUTRRR_URL |
β | Shoutrrr URL (see examples below) |
DEFAULT_SHOUTRRR_STOCK_REMINDERS |
true |
Send stock warnings via push |
DEFAULT_SHOUTRRR_INTAKE_REMINDERS |
true |
Send intake reminders via push |
These defaults are applied when a new user is created. Once a user saves settings in the app, their values take precedence.
Complete list and details:
ntfy (free, self-hostable):
ntfy://ntfy.sh/your-topic
ntfy://user:password@your-server.com/topic
Pushover (free app for iOS/Android):
pushover://shoutrrr:API_TOKEN@USER_KEY/
Get your keys at pushover.net:
- User Key: Shown on your dashboard (top right)
- API Token: Create an application β copy the API Token
Gotify (self-hosted):
gotify://your-server.com/TOKEN
gotify://your-server.com:443/path/to/gotify/TOKEN?priority=1
Discord:
discord://TOKEN@WEBHOOK_ID
Telegram:
telegram://TOKEN@telegram?chats=CHAT_ID
telegram://TOKEN@telegram?chats=@your_channel,-1001234567890
For all services and options, see the Shoutrrr documentation.
docker compose -p medassist-dev -f docker-compose.dev.yml up- Frontend:
http://localhost:5173(hot reload) - Backend:
http://localhost:3000 - API docs UI:
http://localhost:3000/docs(when docs are enabled) - OpenAPI JSON:
http://localhost:3000/docs/json(when docs are enabled)
Useful local commands:
npm run lint
cd backend && npm run test:run
cd frontend && npm run test:runThis project was inspired by MedAssist by njic.









