Vercel

A Vercel deployment pairs PostgreSQL with Vercel Cron. The overlay adds one cron route per job, guarded by a bearer secret, and a vercel.json that schedules all three.

bun create @heyo-sh/heyo-status my-status-page \  --template next --deployment vercel --database postgres

Cron routes

import { vercelCronHandler, type VercelCronTask } from "@heyo-sh/heyo-status/deployments/vercel";import { statusPage } from "../../../../heyo-status.config";const tasks = new Set<VercelCronTask>(["checks", "summarize", "cleanup"]);export async function GET(request: Request, { params }: { params: Promise<{ task: string }> }) {  const { task } = await params;  if (!tasks.has(task as VercelCronTask)) {    return Response.json({ error: "Not found" }, { status: 404 });  }  return vercelCronHandler(statusPage, task as VercelCronTask, {    secret: process.env.CRON_SECRET,  })(request);}

{  "crons": [    { "path": "/api/cron/checks", "schedule": "*/5 * * * *" },    { "path": "/api/cron/summarize", "schedule": "10 0 * * *" },    { "path": "/api/cron/cleanup", "schedule": "0 3 * * *" }  ]}

The schedules must match checks.interval, checks.summaryCron and checks.cleanupCron in the configuration file.

Vercel sends Authorization: Bearer $CRON_SECRET with scheduled invocations. The comparison is constant-time.

Responses

curl -H "authorization: Bearer $CRON_SECRET" https://status.acme.com/api/cron/checks

Deploy

1. 1

   Provision PostgreSQL

   Vercel Postgres, Neon, Supabase or any managed instance. Prefer a pooled connection string for serverless functions.

2. 2

   Set environment variables

   Variable	Purpose
   DATABASE_URL	PostgreSQL connection string.
   CRON_SECRET	Bearer secret for the cron routes.
   HEYO_STATUS_API_TOKEN	Bearer token for /admin/*.

   Set them for Production, Preview and Development as needed.

3. 3

   Migrate

   bashCopy

   DATABASE_URL=… bun run db:migrate

   Run it once per environment before the first deploy, and again after upgrading the package. Request handlers never migrate automatically.

4. 4

   Deploy and verify

   bashCopy

   vercel deploy --prodcurl https://status.acme.com/api/heyo-status/healthzcurl -H "authorization: Bearer $CRON_SECRET" https://status.acme.com/api/cron/checks

Notes for serverless

• The function filesystem is ephemeral and read-only, which is why SQLite is not offered for this target.
• The snapshot cache lives inside one instance. It still removes repeated reads within an invocation burst.
• Keep the connection pool small and pooled; a status page issues only a handful of queries per request.
• Cron frequency is bounded by your Vercel plan, regardless of what the configuration says.
• tcp and ssl monitors work on Vercel's Node runtime — use Node.js 20.19+ so node:net and node:tls resolve.

Other frameworks

The same overlay exists for each template: