Kill the 1-hour wall

Stop letting Vercel
swallow your logs.

Vercel keeps dashboard logs for 1 hour on Hobby and just 1 day on Pro (full retention breakdown). FlareLog keeps your Next.js, Serverless and Edge logs for up to 90 days and turns errors into issues you can fix. On Vercel Pro or Enterprise, connect a log drain with no code change. On any plan, add the SDK.

npm install @flarelog/sdk

Free up to 25,000 logs/mo · no card needed

You shipped on Vercel. But at 2am your function errors and the logs are already gone.

Vercel's built-in logging is fine for quick checks. It's not built for incident response, cost debugging, or asking your AI why a production checkout failed. FlareLog is.

Two ways to connect

No code, or one small SDK.
Both take minutes.

Vercel Pro and Enterprise

Log drain, no code

Connect Vercel from your FlareLog project's settings and Vercel sends your function, edge and build logs straight to FlareLog. No SDK, no redeploy. Thrown errors and crashed requests become issues with the stack and a fix prompt for your AI.

  • ✓ One drain can cover every project in your team
  • ✓ Routine request logs are skipped, so they don't use your quota
  • ✓ Visitor IPs and user agents aren't stored
Any plan, including Hobby

The FlareLog SDK

Vercel only offers drains on Pro and Enterprise, so on Hobby the SDK ships your logs as they happen. It also adds what a drain can't: structured fields you choose on each log, and AI call tracking with the cost of each call.

  • ✓ One package for Next.js, Serverless, Edge and Middleware
  • ✓ Tracks AI calls, tokens and cost
  • ✓ You can use both: the drain and the SDK together

Setting up the SDK

1

Install the SDK

Run npm install @flarelog/sdk. One package covers Next.js, Vercel Serverless, Edge, and Middleware.

2

Set your API key

Add FLARELOG_API_KEY as a Vercel environment variable. The SDK auto-detects Vercel's runtime env vars.

3

Wrap your handler

Use withNextRouteHandler for Next.js Route Handlers, or withVercelServerless / withVercelEdge for raw Vercel routes.

4

Connect MCP (optional)

Paste the MCP config into Cursor, Claude Desktop, or Lovable and ask your AI "why did /api/checkout fail?" using live production logs.

app/api/checkout/route.ts
import { flarelog } from "@flarelog/sdk";
import { withNextRouteHandler } from "@flarelog/sdk/next";

const logger = flarelog({ apiKey: process.env.FLARELOG_API_KEY });

export const POST = withNextRouteHandler(logger, async (request) => {
  const body = await request.json();
  logger.info("Checkout started", { cartId: body.cartId });

  const payment = await stripeCheckout(body);
  logger.info("Payment complete", { paymentId: payment.id });

  return Response.json({ ok: true });
});
.env.local / Vercel dashboard
# Add to your Vercel project
vercel env add FLARELOG_API_KEY

# or paste in the dashboard
FLARELOG_API_KEY=fl_your_api_key
What you get

Built for Vercel's
serverless blind spots

Retention

Days of searchable logs

Stop losing context after one hour. FlareLog gives you 7 days free and 90 days on Pro so you can debug last week's incident without replaying traffic.

Search

Deep JSON querying

Filter by stripeEvent, Prisma query, App Router path, or any nested field. Vercel's text-only search can't do that.

Async

No dropped background logs

Background work like webhooks and waitUntil often vanish when a serverless function freezes. FlareLog flushes them before the invocation ends.

Predictable pricing

Traffic spikes shouldn't
punish your observability bill.

Vercel meters observability events alongside requests. One bot swarm or Product Hunt launch can inflate both. FlareLog buckets your logs for a flat $19/mo up to 1M logs.

Capability
FlareLog logoFlareLog
Vercel Logs
Log retention
7 days free, 90 days on Pro
~1 hour on Hobby; paid plans still limited
Search / filtering
Full structured JSON deep query
Basic text search
Async logs (waitUntil, background jobs)
Captured reliably via SDK flush
Dropped when function freezes
Pricing during traffic spikes
$19/mo Pro flat bucket up to 1M logs
Event-based metering → bill shock
Cost burn dashboard
Real-time per-request cost alerts
Not available
AI-native debugging
MCP server for Cursor / Claude / Lovable
Browser-only workflow

Bot traffic

A scraper hitting every route can generate millions of log events. FlareLog's Pro bucket absorbs that instead of multiplying your bill.

Launch day

Product Hunt traffic is a good problem until your logging bill grows with it. A flat rate keeps launch day predictable.

DDoS resilience

You can't stop every attack, but you can stop one from turning into a five-figure observability invoice. Your costs stay bounded.

AI debugging

Ask your AI why it broke.
In the editor.

FlareLog's MCP server connects Cursor, Claude Desktop, or Lovable Agent to your real Vercel logs. No browser tab, no manual grep, no copy-pasting stack traces.

  • "Show me every Stripe webhook failure today"
  • "Why is /api/slow 500ing in production?"
  • "List all error spikes in the last hour"
  • One config block, the same URL and key in every MCP client
Connect MCP server
.cursor/mcp.json
{
  "mcpServers": {
    "flarelog": {
      "url": "https://mcp.flarelog.dev",
      "headers": {
        "Authorization": "Bearer fl_your_api_key"
      }
    }
  }
}

Cursor format. Other MCP clients use the same URL and bearer token.

FAQ

Questions Vercel users
actually ask

Does this replace Vercel Analytics or Monitoring?

No, it sits alongside them. Vercel gives you traffic and Web Vitals. FlareLog gives you searchable structured logs, error grouping, cost burn alerts, and AI-native debugging.

Will this slow down my Vercel functions?

The SDK adds sub-millisecond overhead. Logs are batched and flushed asynchronously, so request latency stays untouched.

Does it capture Edge Function logs too?

Yes. Use withVercelEdge for Edge Functions and Middleware. It runs natively on the Edge runtime with zero dependencies.

What about Next.js App Router?

Export onRequestError from instrumentation.ts using createOnRequestError to capture every server error, including Server Actions. Wrap Route Handlers with withNextRouteHandler. See FlareLog for Next.js.

Do I have to install the SDK?

Not on Vercel Pro or Enterprise. Connect a Vercel log drain from your FlareLog project's settings and your function, edge and build logs arrive with no code change. Add the SDK as well if you want your own structured fields or AI call and cost tracking.

Do I need to change my Vercel subscription?

No. On Hobby, use the SDK: it ships logs with one environment variable. On Pro and Enterprise you can also use a log drain, which needs no code.

Can I try it for free?

Yes. Start with 25,000 logs/mo and 7-day retention on the free tier. Upgrade to Pro when you need 1M logs/mo, 90-day retention, Slack alerts, and the cost burn dashboard.

Start today

Stay on Vercel.
Keep 90 days of logs.

Free tier includes 25,000 logs/month and all core features. No credit card. Connect a Vercel log drain with no code, or add the SDK on any plan.