Deploy and Host Cycling Coach on Railway

Cycling Coach is an open-source, BYOK Telegram bot for cyclists. It syncs with intervals.icu and uses an LLM to answer training questions, inspect recent load, and help plan cycling workouts. This template runs your own single-tenant instance from the public GHCR image.

About Hosting Cycling Coach

This Railway template deploys ghcr.io/yerzhansa/cycling-coach:stable as a long-running worker. Telegram updates are received by outbound long polling, so no public HTTP endpoint is required. Railway mounts a persistent volume at /data for config and local state. The app reads all secrets from Railway variables; the project maintainer does not receive your API keys, Telegram messages, intervals.icu data, or volume contents.

Common Use Cases

• Run a private AI cycling coach in Telegram without managing a VPS.
• Connect intervals.icu activity data to coaching conversations.
• Keep a persistent, single-tenant bot that updates through Railway image auto-updates.

Dependencies for Cycling Coach Hosting

• A Railway account.
• A Telegram bot token from BotFather.
• An intervals.icu API key and athlete ID.
• An API key for one supported LLM provider.
• LLM_PROVIDER set to one of: anthropic, openai, google, deepseek, qwen, minimax, kimi, zai, or openrouter.

Deployment Dependencies

• Source and docs: https://github.com/yerzhansa/cycling-coach
• Docker image: https://ghcr.io/yerzhansa/cycling-coach
• intervals.icu settings: https://intervals.icu/settings
• Telegram BotFather: https://t.me/BotFather

Why Deploy Cycling Coach on Railway?

Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Cycling Coach on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.