FeaturesPricingBlogReserve early access
Now in beta — free during launch

Know before your users when an endpoint fails.

Your /api/checkout returns 504 at 3am. You find out the next morning from a support ticket. That's 6 hours of silent downtime — lost revenue, angry users, and a bug you could have caught in seconds.

Every hour of undetected API downtime costs you users, trust, and money.

External uptime checks from 4 global regions every minute + internal execution monitoring from inside your Next.js server. The only tool that does both. No agents. No YAML. Slack, email or WhatsApp alerts in seconds — not hours.

Early access before public launch
Pro plan free for the first 3 months
Locked pricing for early adopters

Cancel anytime before launch. No credit card required.

npm install @nurbak/watch · Zero dependencies · < 10KB

Next.js API monitoring from inside your server.

Nurbak Watch is an open-source API monitoring tool built specifically for Next.js applications. It runs inside your server process using the Next.js instrumentation hook, executing real internal health checks on every API route — not external synthetic pings.

Zero Config Setup

Install in your Next.js project with zero dependencies. No agents, no YAML, no complex configuration pipelines.

5lines of code

Global Monitoring

Health checks every 60 seconds from 4 regions worldwide. Alerts via Slack, email, or WhatsApp in under 10 seconds.

4global regions

Real Execution Data

Track P50, P95, and P99 latency from actual server execution. Monitor 4xx/5xx error rates and uptime per route.

< 10salert delivery

Built for developers, not for enterprises.

You don't need a $50k/year observability platform to know if your API is healthy.

Already using Sentry or UptimeRobot? Use both.

Sentry catches errors after they happen. UptimeRobot pings your URL from outside. Nurbak Watch is the only tool that combines external uptime checks from 4 global regions with internal execution monitoring from inside your Next.js process — uptime + performance in one place. Complementary, not replacements.

FeatureDatadog / Others Nurbak Watch
Setup time30-60 minutes5 minutes
ConfigurationYAML + agents5 lines of code
Monitoring typeExternal syntheticInternal execution
PricingStarts $23/host/moFree tier
DependenciesAgent + SDK + configZero dependencies
TargetPlatform teamsDevs & small teams

Integration

Five lines. That's it.

Paste this into your instrumentation.ts file. No config files, no YAML, no agents.

instrumentation.ts
import { initWatch } from '@nurbak/watch'

export function register() {
  initWatch({
    apiKey: process.env.NURBAK_WATCH_KEY,
  })
}
Zero config
Silent fail
Zero dependencies

Everything you need. Nothing you don't.

Simple, transparent pricing

Start free. Scale as you grow.

Free

$0/mo

Perfect for developers who want to get started.

Reserve spot

No credit card required

Most Popular

Pro

$29/mo

For teams that need fast health checks and multi-region monitoring.

Reserve spot

No approval needed

Team

$99/mo

For teams that need unlimited projects and collaboration.

Reserve spot
FreeProTeam
Plans
Projects15Unlimited
Endpoints320100
Check intervalEvery 5 minEvery 1 minEvery 1 min
Monitoring regions1 region4 regions4 regions
Monitoring
Health checks
Uptime tracking (30 days)
SSL certificate monitoring
Response time metrics
Multi-region monitoring
Features
Alert channelsEmail onlyEmail, WhatsApp, SMSEmail, WhatsApp, SMS
Team roles
Global search (Cmd+K)
API access
Priority support

Frequently asked questions

What is Next.js API monitoring?

Next.js API monitoring is the practice of continuously checking the health, performance, and availability of API routes built with Next.js (the /api directory or App Router route handlers). Nurbak monitors these routes from inside the server process every 60 seconds, tracking response time, error rates, and uptime across 4 global regions.

How do I set up monitoring for my Next.js app?

Add 5 lines of code to your instrumentation.ts file and deploy. Nurbak auto-discovers all your API routes — no YAML, no agents, no manual endpoint configuration. Setup takes under 5 minutes compared to 30-60 minutes for tools like Datadog or New Relic.

How is Nurbak different from Datadog or Vercel Analytics?

Nurbak runs inside your Next.js server, executing real internal health checks rather than external synthetic pings. This catches issues that external monitors miss, like slow database queries or failing middleware. It costs $0-29/month vs $23+/host/month for Datadog, requires zero configuration vs YAML + agents, and delivers alerts in under 10 seconds.

Does Nurbak work with the App Router and Pages Router?

Yes. Nurbak supports both the Next.js App Router (route.ts handlers) and the Pages Router (/api directory). It auto-discovers routes in both patterns and monitors them identically. No changes to your route code are needed.

What alert channels does Nurbak support?

Nurbak sends alerts via Slack, email, and WhatsApp (Pro plan). Alerts are delivered in under 10 seconds from the moment a health check fails. You can configure different alert rules and thresholds per endpoint, and route notifications to different channels per severity.

Is Nurbak free?

Yes. The free tier includes 1 project, 3 endpoints, and 5-minute check intervals with email alerts — no credit card required. The Pro plan at $29/month adds 5 projects, 20 endpoints, 1-minute checks from 4 global regions, and WhatsApp/SMS alerts.

Do I need this if I already have Sentry?

Yes. Sentry is error tracking. Nurbak Watch is uptime and performance monitoring. Sentry tells you what broke after an exception is thrown. Nurbak tells you when something is slow or down — even before it throws an error. They are complementary, not competitors. Use Sentry for errors. Use Nurbak Watch for uptime and latency.

How is Nurbak different from UptimeRobot?

UptimeRobot pings your URL from outside. It can't see inside your server. A route can return 200 and still be processing for 3 seconds because of a slow database query — UptimeRobot will say everything is fine. Nurbak Watch combines external pings from 4 regions with internal monitoring from inside your Next.js process, so you see real latency, real error rates, and real execution data per route. One less tool in your stack.

Why Next.js only?

Because doing one thing well beats doing everything badly. Next.js has a specific instrumentation API (instrumentation.ts) that lets us monitor from inside the server process without performance overhead. We built around that. Other frameworks are coming after we nail Next.js.

Start monitoring your Next.js APIs today.

Free during beta. No credit card required.

No spam. Unsubscribe anytime.