Overview

Connect Interfere to where your code lives, where it runs, and where your team talks.

Integrations give Interfere the context around your code and a way to reach your team. You connect and manage them from Settings → Integrations.

They fall into three groups:

• Sources are where your code lives, so Interfere can tie a problem to the change that caused it.
• Destinations are where your code runs, so Interfere can line a problem up with the release that shipped it.
• Communications are how Interfere reaches your team and takes direction back.

Deploying somewhere without a native integration, like AWS (CodeBuild, ECS, EC2, Lambda), Fly, Render, or your own servers? Use the CLI to report releases and upload source maps from your pipeline — see AWS, Fly, Render, and self-hosted deploys for a worked example.

Interfere requests the least access each integration needs, and read-only wherever possible. Each page lists the exact permissions and why.