Deployment Overview

​

Architecture

┌─────────────────┐     ┌──────────────┐     ┌─────────────────┐
│   Next.js App   │────>│   Database   │<────│  Scheduler(s)   │
│  (Dashboard UI) │     │ (SQLite/PG)  │     │ (Monitor Runner) │
└─────────────────┘     └──────────────┘     └─────────────────┘

​

Components

• Next.js App: Web dashboard for viewing monitors, managing alerts, and accessing status pages
• Database: Shared data store (SQLite or PostgreSQL) for all configuration and check results
• Scheduler: Standalone service that executes monitors on schedule, evaluates alerts, and dispatches webhooks

​

Deployment Scenarios

​

Choosing a Deployment Option

​

Vercel

• Teams already using Vercel
• Serverless infrastructure preference
• Automatic scaling requirements
• Fast global CDN delivery

• Vercel Cron runs every 30 seconds minimum
• Requires PostgreSQL (not SQLite)
• Cold starts may affect monitor timing

​

Fly.io

• Always-on persistent VMs
• Multi-region deployments
• Fine-grained control over scheduling
• SQLite or PostgreSQL support

• Requires Fly.io account
• Manual scaling configuration
• Pay for always-running machines

​

Docker

• Containerized environments
• Local development and testing
• Docker Compose orchestration
• Consistent deployment across platforms

• Requires Docker knowledge
• Manual container orchestration
• Volume management for persistence

​

Self-Hosted

• Complete infrastructure control
• On-premises requirements
• Custom VPS configurations
• Integration with existing infrastructure

• Manual server setup and maintenance
• Requires reverse proxy configuration
• Process management setup needed

​

Multi-Region Deployments

PONGO_REGION=us-east bun scheduler   # Region 1
PONGO_REGION=eu-west bun scheduler   # Region 2

alerts: [
  {
    id: "api-down",
    name: "API Down",
    condition: { consecutiveFailures: 3 },
    regionThreshold: "majority", // "any" | "all" | "majority" | number
  },
]

​

Database Options