ADR-0008: Use Supabase for Managed PostgreSQL Hosting
Status
Accepted
Date
2026-05-30
Context
ADR-0007 selected PostgreSQL as the primary database for WatchTower to support the project’s transition from a local prototype to a hosted application.
While PostgreSQL provides a suitable production database solution, self-hosting PostgreSQL would require:
- database provisioning
- infrastructure management
- backups and recovery configuration
- monitoring and maintenance
- security configuration
WatchTower’s primary focus is observability and telemetry functionality rather than database administration.
The project requires a managed PostgreSQL solution that simplifies deployment while remaining compatible with the existing Node.js backend architecture.
Decision
Use Supabase as the managed PostgreSQL provider for WatchTower.
Supabase will provide:
- managed PostgreSQL hosting
- database administration tools
- automated backups
- secure database access
- cloud-hosted infrastructure
WatchTower will continue to interact directly with PostgreSQL through the backend application.
Rationale
- Supabase provides fully managed PostgreSQL infrastructure
- Reduces operational overhead associated with database administration
- Simplifies deployment and maintenance
- Includes useful database management and monitoring tools
- Supports secure remote access from the hosted backend
- Allows the development team to focus on application functionality rather than infrastructure management
- Provides a free tier suitable for academic and MVP development
Alternatives Considered
Self-Hosted PostgreSQL
Rejected because managing database infrastructure would introduce additional operational complexity that is outside the project’s primary scope.
Railway PostgreSQL
Rejected because Supabase provides a more mature PostgreSQL management experience and additional tooling useful during development.
Neon
Rejected because while Neon provides hosted PostgreSQL, Supabase offers a broader ecosystem of management tools and developer features that simplify database administration.
Consequences
Positive
- Reduced infrastructure management burden
- Managed backups and maintenance
- Simplified deployment process
- Production-ready PostgreSQL hosting
- Easy integration with existing backend architecture
- Suitable for MVP and future project growth
Negative
- Introduces dependency on a third-party hosting provider
- Potential vendor lock-in
- Service availability depends on Supabase infrastructure
- Future pricing may impact long-term deployment decisions
Conclusion
Supabase was selected because it provides a managed PostgreSQL platform that aligns with WatchTower’s hosted deployment architecture while minimizing operational complexity. This allows the team to focus on observability functionality rather than database administration.