ADR-0009: Use Render for WatchTower Application Hosting
Status
Approved
Date
2026-05-30
Context
WatchTower requires a hosting solution for its deployed application components, including:
- frontend dashboard
- Node.js backend API
- telemetry ingestion endpoints
The hosting platform must:
- support full-stack deployment
- support long-running backend services
- integrate easily with GitHub
- provide a straightforward deployment workflow
- align with the project’s hosted architecture goals
As WatchTower transitions from a local prototype to a hosted observability platform, a deployment solution is needed that can host both the frontend and backend components in a single ecosystem.
Decision
Use Render as the primary hosting platform for WatchTower.
Render will host:
- the frontend application
- the Node.js backend service
- deployment infrastructure required for telemetry ingestion and dashboard functionality
Rationale
- Render provides managed hosting for both static sites and backend services
- Supports Node.js applications without requiring significant infrastructure configuration
- Integrates directly with GitHub for automated deployments
- Simplifies deployment and maintenance workflows
- Provides a centralized platform for hosting WatchTower services
- Reduces operational complexity compared to self-managed infrastructure
- Suitable for MVP
Alternatives Considered
GitHub Pages
Rejected because GitHub Pages only supports static site hosting and cannot host the WatchTower Node.js backend or telemetry ingestion endpoints.
Vercel
Rejected because while Vercel provides excellent frontend hosting, its architecture is more heavily optimized for frontend and serverless workloads. Render provides a more straightforward environment for hosting a persistent Node.js backend service alongside the frontend application.
Consequences
Positive
- Simple deployment workflow
- Native support for Node.js backend services
- GitHub integration with automatic deployments
- Centralized hosting platform for frontend and backend components
- Reduced infrastructure management burden
Negative
- Dependency on a third-party hosting provider
- Service availability depends on Render infrastructure
- Potential future pricing considerations
- Some platform-specific deployment configurations may create migration effort if another hosting provider is adopted later
Conclusion
Render was selected because it provides a straightforward hosting platform that supports both WatchTower’s frontend and backend requirements while minimizing deployment complexity. Its support for persistent Node.js services and GitHub-based deployment workflows makes it a strong fit for WatchTower’s hosted architecture.