Skip to main content
This guide takes you from a new account to your first issue. You need an app that you can run locally or deploy. You can connect it in four ways:
  • SDK: Next.js, Node.js, or the browser. Sends errors with stack traces.
  • Log drain: Vercel, Railway, Render, and other hosts. No code changes.
  • OpenTelemetry: any language with an OTLP exporter, including Python, Go, and Rust.
  • Coding agent: copy one prompt into your coding agent, and it does the setup. See Set up with a coding agent.
For the first three, follow the steps below. Connect your app has a tab for each.

Create an account

  1. Open app.squasher.ai/signup.
  2. Enter your email and select Create account.
  3. Open the sign-in link that Squasher sends to your email. There is no password.
Next time, you can also sign in with Continue with Google.

Create your organization and project

After your first sign-in, Squasher asks for three things:
  1. An organization name, for example your company.
  2. A project name, for example the service you want to monitor.
  3. A platform. This one is optional.
Select Create project. Squasher makes you the owner of the organization and opens the new project’s Setup page. If you join an organization that has no projects, owners and admins see the same form. Other members see a message to ask an owner for access.

Create an ingest key

On the Setup page of your project:
  1. Under 1. Create an ingest key, select Create ingest key. Squasher shows the key only once.
  2. Save the key in your secret store as SQUASHER_API_KEY.
  3. Under 2. Connect your application, select Manual. Save the Project ID as SQUASHER_PROJECT_ID.
Only owners, admins, and security admins can create keys. If your workspace shows No projects yet, ask an owner of your organization to give you access to a project.

Connect your app

1

Install the SDK

Add SQUASHER_API_KEY and SQUASHER_PROJECT_ID to .env.local.
2

Create instrumentation.ts

Add this file to your project root, or to src/ if you use a src folder.
instrumentation.ts
The SDK runs on the Node.js runtime only. It does not capture errors on the Edge runtime.
3

Send a test error

Create a route that throws, then open /api/squasher-test once.
app/api/squasher-test/route.ts
For middleware, Server Components, and the browser, see the Next.js SDK.

See your first issue

  1. On the Setup page, under 3. Verify a signal, select Check again. When Squasher finds an event from the last 24 hours, the page shows Recent event received.
  2. Select Issues in the sidebar. Your test error is at the top of the list.
  3. Open the issue to see its event count, when it was first and last seen, and the AI triage summary.
AI triage runs on its own for new issues in the production environment. To triage your test error, open the issue and select Run triage in the Squasher triage card. If the error does not appear, see Troubleshooting.

Next steps

Set up notifications

Send incidents to Slack, PagerDuty, email, or Telegram.

Read AI triage

Learn what the triage summary tells you.

Add uptime monitors

Check your endpoints and open incidents when they fail.

Connect GitHub

Link a repository so that auto-fix can open pull requests.