Self-hosted
For teams who want inspectable code and their own infrastructure.
- Open source (AGPL-3.0)
- Runs on your infrastructure
- Core monitoring and verification
- Status pages and integrations
- You manage upgrades, workers, and backups
Self-host
Deploy the same core monitoring system behind Fajita Cloud using Docker, your own database, workers, notifications, and domain.
Requirements
Architecture
Web app, PostgREST, PostgreSQL, Go monitor worker, and scheduler sidecar. Alert worker recommended.
Web (Next.js) PostgREST PostgreSQL Go monitor worker Scheduler sidecar Alert worker (recommended)
Quick start
git clone https://github.com/Accomplish-Labs/fajita-io.git
cd fajita-io
cp .env.example .env
docker compose up -dSet FAJITA_DEPLOYMENT_MODE=self_hosted, Clerk keys, and encryption secrets in .env before signing in. Run npm run selfhost:doctor to validate configuration.
Operations
Infrastructure and networking
Database backups and restore testing
Application and worker upgrades
TLS certificates and reverse proxy
Secret rotation and access control
Email delivery configuration
Upgrades follow repository releases and migration files. Test backups on a schedule you trust.
Security
Self-hosted operators control their infrastructure and secrets. Private network monitoring requires an explicit opt-in. Follow self-hosting security guidance and the repository SECURITY.md link for disclosure.
How to run Fajita
Run Fajita yourself for full control, or let Fajita Cloud handle the infrastructure.
For teams who want inspectable code and their own infrastructure.
For teams who want monitoring without operating workers or databases.
Fajita Cloud
Fajita Cloud runs workers, upgrades, backups, and notifications for you.