Deploy Tronbyt — Tidbyt Alternative
Self-hosted Tidbyt alternative for managing smart display apps.
tronbyt-server
Just deployed
/app/data
Redis
Just deployed
/data
Deploy and Host Tronbyt Server on Railway
Tronbyt Server is a self-hosted server for managing smart display apps and content. It provides a web interface, application management, device integration, persistent storage, and caching in a compact deployment that works well as a self-hosted alternative for Tidbyt-style display environments.

About Hosting Tronbyt Server
This template deploys Tronbyt Server with Redis and persistent storage.
Tronbyt provides the main web application and server runtime, while Redis is used as a persistent cache backend. Application data is stored on a persistent volume so important state survives service restarts and redeployments.
The result is a simple two-service architecture that provides a ready-to-use Tronbyt environment without requiring users to manually configure Redis or storage.
Included Architecture
| Service | Purpose |
|---|---|
| Tronbyt Server | Web interface, display management, apps, and server runtime |
| Redis | Persistent caching backend |
| Tronbyt Volume | Persistent application data |
| Redis Volume | Persistent Redis data |
| Health Check | Monitors Tronbyt availability |
┌─────────────────┐
│ User │
└────────┬────────┘
│
▼
Railway HTTPS Proxy
│
▼
┌─────────────────┐
│ Tronbyt Server │
│ │
│ Apps / Devices │
│ Web Interface │
└───────┬─────────┘
│
┌──────────┴──────────┐
│ │
▼ ▼
Persistent Volume Redis
/app/data Cache
│
▼
/data
Common Use Cases
- Self-host a smart display management server
- Manage display apps from a web interface
- Run a private Tidbyt-style server
- Manage custom display content
- Develop and test display applications
- Keep application data persistent across redeployments
- Use Redis-backed caching for a more resilient deployment
- Run Tronbyt for personal, development, or small-team environments
Tronbyt Server vs Hosted Display Platforms
| Feature | Tronbyt Server | Hosted Display Platform |
|---|---|---|
| Self-hosted | ✅ Yes | ❌ Usually managed |
| Infrastructure control | ✅ Full | ❌ Provider controlled |
| Persistent storage | ✅ Yes | ✅ Managed |
| Redis caching | ✅ Included | ⚠️ Provider dependent |
| Web interface | ✅ Yes | ✅ Usually |
| Open deployment | ✅ Yes | ❌ Platform dependent |
Tronbyt Server is especially useful when you want control over your smart display backend, application data, and deployment environment.
Persistent Storage
This template includes persistent storage for both Tronbyt and Redis.
Tronbyt Server
Application data is stored under:
/app/data
This allows configuration and application state to survive service restarts and redeployments.
Redis
Redis uses persistent storage at:
/data
Redis acts as the cache backend for Tronbyt, avoiding reliance on application-only in-memory caching.
Health Check
The template includes an application health check using:
/health
This allows Railway to verify that Tronbyt Server is responding correctly before routing traffic to the service.
Getting Started
After deployment:
- Wait until both Tronbyt Server and Redis are online.
- Open the public Railway domain assigned to Tronbyt Server.
- Create your account.
- Sign in to the Tronbyt web interface.
- Configure your display environment.
- Add or manage supported applications.
- Connect your display or compatible client.
- Start managing content from the Tronbyt dashboard.
User registration is enabled by default in this template.
GitHub Integration
Tronbyt can optionally use a GitHub token for functionality that interacts with GitHub repositories or APIs.
If required, open the Variables section of the Tronbyt service and provide:
GITHUB_TOKEN
This is optional and is not required for the basic deployment.
Redis Caching
This template includes Redis as a dedicated caching backend.
Using Redis instead of application-only memory caching provides a more consistent cache layer and allows cached data to survive application process restarts when Redis persistence is enabled.
The Redis service communicates with Tronbyt over Railway's private network and does not need to be publicly exposed.
Dependencies for Tronbyt Server Hosting
- Tronbyt Server — smart display management server and web interface
- Redis — persistent cache backend
- Tronbyt Persistent Volume — stores application data
- Redis Persistent Volume — stores Redis data
- Railway Private Networking — internal communication between Tronbyt and Redis
- Railway Public Networking — HTTPS access to the Tronbyt web interface
- Health Check — application availability monitoring
Deployment Dependencies
- Tronbyt GitHub: https://github.com/tronbyt/server
- Tronbyt Container: https://github.com/tronbyt/server/pkgs/container/server
- Railway Redis Documentation: https://docs.railway.com/databases/redis
- Railway Networking: https://docs.railway.com/networking
- Railway Volumes: https://docs.railway.com/volumes
Why Deploy Tronbyt Server 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 Tronbyt Server on Railway, you get a self-hosted smart display platform with persistent storage, Redis caching, health monitoring, private networking, and a simple web interface in one deployment.
Template Content
tronbyt-server
ghcr.io/tronbyt/serverRedis
redis:8.2