Use this page as the starting point for installing, operating, and understanding Warden.
- Database configuration — run Warden with SQLite or PostgreSQL.
- Application configuration — configure the listener, database, cookies, and reverse proxy handling.
- Monitor types — configure HTTP, TCP, ping, and DNS checks.
- Notifications — deliver alerts through Slack, Discord, Telegram, webhooks, or email.
- Password recovery — regain access to an installation.
- Why Warden — product focus and the gap Warden is designed to fill.
- Adaptive latency — how each monitor learns its normal response time.
- Notification fatigue — confirmation, reminders, flapping detection, correlation, and alert damping.
- Patterns — recurring behavior and longer-term changes found in monitor history.
- Timezones — choose your timezone and understand how dates appear across Warden.
- Roadmap — product themes and planned areas of investment.
- REST API — API keys, endpoints, and Swagger documentation.
- MCP server — safely inspect and operate Warden through an AI assistant.
- Move PostgreSQL to another instance — dump, restore, verify, roll back, and relearn latency after moving networks.
- Load testing — exercise Warden under sustained check volume.
For local development, tests, and Markdown formatting, see Contributing.