Skip to main content
Railway provides the fastest way to get a production Open Wearables instance running. The template deploys all required services with sensible defaults - no manual infrastructure setup needed. Deploy on Railway
An admin account is created automatically on first startup (admin@admin.com / your-secure-password). To use custom credentials, set ADMIN_EMAIL and ADMIN_PASSWORD on the Backend service before deploying (as shown on the video)

​
What gets deployed

The Railway template provisions seven services: All inter-service networking and environment variables are configured automatically by the template.

​
Post-deploy setup

1

Configure provider OAuth credentials

To enable wearable data syncing, add OAuth credentials for each provider you want to support on the Backend service.
You only need to configure providers you plan to use. See Supported Providers for setup instructions for each one.
2

Set up a custom domain (optional)

Railway assigns a default *.up.railway.app domain to each service. To use your own domain:
  1. Open your Frontend service in Railway
  2. Go to Settings > Networking > Custom Domain
  3. Add your domain and configure the DNS records as shown
Repeat for the Backend service if you want a custom API domain. Then update the following environment variables:

​
Environment variables reference

Key variables you may want to customize on the Backend service:
Database and Redis connection strings are injected automatically by Railway — you do not need to set these manually. REDIS_SSL defaults to false and is only needed if you swap Railway’s built-in Redis for an external managed instance with TLS enabled.

Supported Providers

Configure OAuth credentials for each wearable provider.

API Reference

Explore available API endpoints.