Pulse

Uptime & status monitoring for modern teams — real-time incident detection, alerting that actually reaches you, and branded public status pages.

Status: MVP complete — see ARCHITECTURE.md for the design.

Pulse continuously checks your HTTP endpoints, detects incidents the moment they happen, and keeps your team and your users informed through real-time dashboards, alerts, and shareable status pages.

Features

• Endpoint monitoring — scheduled HTTP/HTTPS checks with configurable intervals, timeouts, and expected status codes.
• Real-time dashboard — live monitor status and incident updates streamed over Server-Sent Events.
• Incident engine — automatic incident open → acknowledge → resolve lifecycle backed by an explicit state machine.
• Uptime & latency analytics — time-series charts for response time and availability (SLA %).
• Alerting — email (Resend) and outbound webhook notifications the moment something breaks.
• Public status pages — branded, shareable status pages per organization.
• Teams & roles — multi-tenant organizations with role-based access control.
• Billing — Stripe subscriptions with plan-based usage limits.

Tech stack

Layer	Choice	Why
Framework	Next.js 16 (App Router, RSC)	One codebase, server-first rendering
Language	TypeScript	End-to-end type safety
Database	PostgreSQL (Neon)	Reliable relational store, serverless-ready
ORM	Prisma 7	Type-safe data access + migrations
Auth	Auth.js v5	Self-hosted sessions + RBAC
Real-time	SSE + Postgres LISTEN/NOTIFY	Live updates without extra infrastructure
Payments	Stripe	Subscriptions + hosted billing portal
Email	Resend	Transactional alerts
Styling	Tailwind CSS v4	Utility-first, fast iteration
Testing	Vitest + Playwright	Unit + end-to-end
CI	GitHub Actions	Lint, typecheck, test, build on every push

Getting started

Prerequisites

• Node.js 22+
• A PostgreSQL database (local or Neon)

Setup

# 1. Install dependencies
npm install

# 2. Configure environment
cp .env.example .env
#   → fill in DATABASE_URL and secrets

# 3. Apply the database schema
npm run db:migrate

# 4. Start the dev server
npm run dev

Then open http://localhost:3000.

Scripts

Command	Description
npm run dev	Start the development server
npm run build	Production build
npm run start	Serve the production build
npm run lint	Lint with ESLint
npm run typecheck	Type-check with tsc --noEmit
npm run test	Run unit tests (Vitest)
npm run test:e2e	Run end-to-end tests (Playwright)
npm run format	Format the codebase with Prettier
npm run db:migrate	Apply database migrations
npm run db:studio	Open Prisma Studio

Architecture

Pulse is a single Next.js application using the App Router and React Server Components. Scheduled checks run as background jobs that write time-series results to Postgres; an incident state machine derives incidents from consecutive failures, and the dashboard subscribes to changes in real time via Server-Sent Events fed by Postgres LISTEN/NOTIFY.

src/
├── app/            # App Router routes (dashboard, public status pages, API routes)
├── components/     # Reusable UI components
├── lib/            # Domain logic (auth, db, monitoring, billing, real-time)
├── server/         # Server-only actions & services
└── test/           # Test setup & utilities
prisma/
└── schema.prisma   # Database schema & migrations

For a deeper dive — data model, key flows, and deployment — see ARCHITECTURE.md.

Testing

• Unit (Vitest) — pure domain logic: RBAC, slug generation, HTTP checks, the incident state machine, uptime/latency stats, sparkline geometry, plan limits, and webhook payloads. Run with npm run test.
• End-to-end (Playwright) — real-browser flows including sign-up → dashboard. Run with npm run test:e2e (boots the dev server automatically; requires a database).

Deployment

Pulse builds to a self-contained server (output: 'standalone') and ships a multi-stage Dockerfile:

docker build -t pulse .
docker run -p 3000:3000 --env-file .env pulse

Because real-time updates use a persistent Postgres LISTEN connection, deploy to a long-running Node server rather than short-lived serverless functions. Point any scheduler at GET /api/cron/run-checks (with the CRON_SECRET bearer token) to drive checks.

Roadmap

• Project foundation — Next.js, Prisma, tooling, CI
• Design system, theming & landing page
• Auth & multi-tenant teams (Auth.js v5, RBAC)
• Monitors & scheduled checks
• Incident engine, charts & real-time dashboard (SSE)
• Alerting (email + webhooks) & public status pages
• Stripe billing (plans, checkout, webhooks, portal)
• Testing (unit + e2e), docs & Docker deployment

License

Released under the MIT License.