Fajita uses one monitoring codebase for self-hosted and Cloud deployments. The operational difference is who runs workers, databases, and mail infrastructure.
Core flow
Scheduler → Workers → Verification → Incident engine → Notifications → Status page, backed by PostgreSQL.
Verification
Failed checks enter verification before incidents open. This is the primary behavioral difference from simple ping monitors.