Fajita is now open source

We built Fajita as a hosted uptime monitor for small software teams. Today we are publishing the core under AGPL-3.0.

You can inspect how Fajita verifies failures, self-host the same engine we run in production, or keep using Fajita Cloud when you would rather not operate workers and databases yourself.

Why we open-sourced it

Monitoring software tells you when something is wrong. You should be able to see how it decides that.

Fajita already focused on clear incident behavior and verification before alerts. Open source is the honest extension of that: same product story, inspectable code.

What is included

• Website, API, SSL, and heartbeat monitoring
• Failure verification before incidents and alerts
• Incidents, maintenance, and public status pages
• Slack, Discord, webhooks, and email (SMTP or Resend)
• Docker Compose self-hosting path

Self-host or Cloud

Self-hosted Fajita is not a demo tier. Cloud is not obsolete. Cloud sells operational convenience: managed workers, upgrades, backups, and notifications.

Run it yourself: Self-hosting guide. Source: GitHub. Managed option: Fajita Cloud.

Verification still matters

Most uptime tools alert on the first failed ping. Fajita re-checks before escalating. Open source does not change that behavior. It makes it reviewable.

That matters when you are choosing what wakes someone up at 2 a.m. You can read the verification path in the repository, run it locally, and decide whether the thresholds match your tolerance for blips versus real outages.

How to get started

Clone the repository, copy .env.example, and bring up Docker Compose. You will need your own Clerk application for authentication. The self-hosting quickstart walks through the full path from empty machine to first monitor.

If you prefer not to run PostgreSQL, workers, and upgrades yourself, Fajita Cloud is the managed option. Same verification engine. We operate the infrastructure.

Contributing

Found a bug or have an idea? Open an issue on GitHub. Want to contribute code? Start with a good first issue. We review external PRs for correctness, security, and maintainability. Open source does not mean design-by-committee.

If you want to follow development, star the repository. If you want it running without operating it, start with Cloud.