What gets deployed
The Railway template provisions seven services:| Service | Description |
|---|---|
| PostgreSQL | Primary database for users, health data, and API keys |
| Backend | FastAPI application server |
| Frontend | React dashboard |
| Redis | Broker for Celery task queue and caching |
| Celery Worker | Processes background tasks (data syncs, webhooks) |
| Celery Beat | Schedules recurring sync jobs |
| Flower | Celery monitoring dashboard |
Post-deploy setup
Configure provider OAuth credentials
To enable wearable data syncing, add OAuth credentials for each provider you want to support on the Backend service.
Set up a custom domain (optional)
Railway assigns a default
*.up.railway.app domain to each service. To use your own domain:- Open your Frontend service in Railway
- Go to Settings > Networking > Custom Domain
- Add your domain and configure the DNS records as shown
| Variable | Service | Value |
|---|---|---|
VITE_API_URL | Frontend | Your backend URL (e.g. https://api.yourdomain.com) |
CORS_ORIGINS | Backend | Your frontend URL (e.g. https://yourdomain.com) |
Environment variables reference
Key variables you may want to customize on the Backend service:| Variable | Description | Default |
|---|---|---|
SECRET_KEY | JWT signing key | Auto-generated by template |
CORS_ORIGINS | Allowed CORS origins (comma-separated) | Frontend Railway URL |
LOG_LEVEL | Application log level | info |
Database and Redis connection strings are injected automatically by Railway — you do not need to set these manually.
Related guides
Supported Providers
Configure OAuth credentials for each wearable provider.
API Reference
Explore available API endpoints.

