Muon

Integrations

Metrics are easier to understand when Muon knows what happened around them — releases, deploys, errors, revenue and mobile subscriptions.

What do Muon integrations do?

Official integrations connect product analytics with code changes, deployments, errors, revenue, mobile subscriptions, support workflows and product operations, so Findings can be investigated with real context.

Community detects what changed; Muon Pro connects it to the systems that explain why.

Planned official integrations

The context that explains a metric.

Grouped by what they bring to the timeline: engineering signals, revenue signals and product operations. Each integration adds timeline events correlated with the metrics you already track.

Engineering

GitHubReleases
GitLabReleases
SentryErrors
VercelDeploys
CloudflareTraffic
SupabaseBackend
FirebaseBackend

Revenue

StripeRevenue
PaddleRevenue
RevenueCatSubscriptions
App Store ConnectMobile
Google Play ConsoleMobile

Operations

SlackNotify
DiscordNotify
LinearIssues
JiraIssues
NotionDocs

Individual per-integration pages are coming: GitHub, Sentry and Stripe are next.

Integration timeline

One deploy, a chain of signals, one Finding.

Integrations feed a shared timeline. When several signals line up around the same moment, Muon can connect them into a single Finding — statistics first, explanation second.

GitHub deploy
Sentry issueerrors +320%
Stripe revenue changecheckout ↓
Cloudflare traffic spikeedge load
Muon Findingcorrelated

Correlation is not causation — Muon surfaces the related signals with confidence and impact so a human can decide what is likely connected.

Community connector SDK

An open connector API for anything you run.

Muon provides an open connector API so teams can add internal systems and community integrations that push timeline events into Muon. Community detects what changed; official supported connectors are part of Muon Pro.

Build your own

The connector API is open and self-hostable. Emit release, deploy, error, revenue or custom events from any internal system and they appear on the timeline alongside your metrics.

Supported by Muon Pro

Official connectors — GitHub, Sentry, Stripe and more — are maintained, authenticated and supported as part of Muon Pro, so you do not have to run the plumbing yourself.

How connecting works

Five steps to a connected timeline.

Connecting any integration follows the same short path from Settings to live timeline events.

Open Settings → Integrations

Head to the Integrations panel in your Muon project settings.

Choose the integration

Pick from the official catalogue or point Muon at a custom connector you built with the open API.

Authorize access

Grant read access via OAuth or an API token so Muon can receive the relevant events.

Select projects and environments

Map the integration to the Muon projects and environments where its events belong.

Start receiving timeline events

Releases, deploys, errors and revenue changes flow onto the timeline and become available for Findings.

FAQ

Questions, answered directly.

Which integrations does Muon support?
Planned official integrations include GitHub, GitLab, Sentry, Vercel, Cloudflare, Stripe, RevenueCat, Slack, Linear, Jira and more — grouped into engineering, revenue and operations.
Are integrations free?
Teams can build their own integrations for free via the open connector API. Official supported connectors are part of Muon Pro.
Can I build a custom integration?
Yes — Muon provides an open connector API so teams can add internal systems and community integrations that push timeline events into Muon.
What does an integration add?
An integration adds timeline events correlated with product metrics for investigation and insight summaries.
Connect the context

Give your metrics the context to explain themselves.

Community detects what changed. Add official integrations with Muon Pro, or build your own with the open connector API.