Skip to main content
Vercel drains are the fastest way to get coverage, but the Squasher SDK gives you better stack frames, user context, breadcrumbs, release tags, and manual capture control.

​
Setup

1

Keep the drain live

Leave your existing Vercel drain in place while you install the SDK so you do not lose infrastructure and runtime coverage during rollout.
2

Install the SDK in the app

Add the SDK for your stack, then capture unhandled exceptions and any custom errors you want surfaced with richer metadata.
3

Tag releases and environments

Make sure the SDK sends release and environment values so issues line up with deploys and previews.

​
Verify

  • Trigger one handled exception through the SDK and one platform-level failure through the drain.
  • Confirm the SDK event shows richer fields than the drain event.
  • Confirm duplicate incidents are not created for the same application failure.

​
Migrate

  • Keep both paths during rollout.
  • Move primary alerting to SDK-based issues once application coverage is complete.
  • Keep the drain for infrastructure, edge, and platform logs that the SDK cannot see.

​
Hot-swap

  • Do not remove the drain unless you have another source for deployment and platform logs.
  • Roll the SDK out route by route or service by service if the app is large.
  • Verify one real deploy before changing paging rules.

​
Agent handoff