Skip to main content
Create a workspace, install the SDK in your app, and check that Interfere receives events.

​
Create a workspace

Open setup. Choose a workspace name, URL slug, and company email domain. The slug identifies your workspace in links and API requests. For interfere.com/~/acme, it is acme. New workspaces use Unrestricted data residency. Storage and processing are not restricted to a specific region. Use your team’s email domain so colleagues can join through your workspace domain settings.

​
Add your app

Create a surface for the app you want to monitor. Give separately deployed apps their own surfaces, such as a storefront and its backend API. Choose the framework and copy the surface’s public key. The SDK uses it to send telemetry. Copy the secret API key to your build environment for release registration and source maps.

​
Install the SDK

Follow one guide through its verification step:

Next.js

App Router, browser capture, and server instrumentation.

Vite + React

React apps built with Vite.

TanStack Start

Browser and server capture for Start.

NestJS

Request errors and tracing in NestJS.

Node.js

Services, background workers, and scripts.

​
Connect your code and deployment

Connect GitHub and select the repository for your surface. This gives investigations access to the code behind an error. Connect Vercel or Cloudflare Workers if you deploy there, then map the project or Worker to your surface. For other hosts, the SDK build plugins publish release metadata and source maps.

​
Verify events

Build and deploy the app with its public key and an environment label such as staging. Run the test capture in your SDK guide, then open the surface in Surfaces. The event chart should show incoming traffic. Setup’s Events step completes when the first event arrives. Finish the remaining setup steps, including selecting a plan. The event chart confirms delivery; problems appear as Interfere detects and investigates issues.

​
Open your first investigation

Open the Inbox, select the surface and environment you just deployed, and open a detected problem. In Timeline, read the explanation. In Findings, open an occurrence and inspect its error and stack frames. For browser problems, open Sessions to replay the actions around the failure. Follow Investigations for a worked example showing how to check the explanation against a trace, a release, and an affected session.