Muon

Mobile app analytics

Muon is designed around projects and events, not just websites — connect web, app and revenue journeys in one platform.

Does Muon support mobile apps?

Muon is designed around projects and events, so a project can include a website, an iOS app, an Android app, a backend service and a desktop app.

Web is the first platform; iOS, Android and backend SDKs are planned.

One project, every platform

A project is a product — not a single website.

Because Muon models events against a project rather than a domain, everything a product touches can report into the same place. Web ships first; the other platforms follow as SDKs land.

WebsiteAvailable
iOS appPlanned SDK
Android appPlanned SDK
Backend servicePlanned SDK
Desktop appPlanned SDK

Web is live today. iOS, Android, backend and desktop are addressed through planned SDKs — designed around the same project-and-event model.

Cross-platform journeys

Track product journeys across platforms.

When web, app and revenue events share one project, a single journey can move from an ad click all the way to a paid subscription — without stitching separate tools together.

Google Ads

A campaign click brings a prospect toward the product.

Landing page

The web tracker records the visit and the page they arrive on.

Signup

The visitor becomes a known user with a shared identity across platforms.

iOS install

The same user installs the mobile app — reported by the planned Swift SDK.

First session

Their first in-app session continues the journey inside the same project.

Subscription

A revenue event via RevenueCat, the App Store or Google Play closes the loop.

Planned SDKs

SDKs for the languages your product speaks.

These SDKs are planned or in progress — not all are available yet. The Swift SDK is the reference template the others follow, so each new SDK stays consistent with the same project-and-event model.

JavaScriptSwiftKotlinNode.jsPythonGoRustPHP

The Swift SDK is the reference template; the remaining SDKs are planned or in progress. Don't take a listing here as a shipped availability guarantee.

Revenue & subscriptions

Connect installs and subscriptions to the journey.

Mobile revenue lives in the app stores. Muon connects it through integrations, so subscription events land in the same project as web and product events — and a conversion drop can be tied back to the release or segment behind it.

RevenueCat

Subscription lifecycle events flow in, so renewals, trials and churn appear alongside product usage.

App Store

iOS purchases and subscriptions connect to the same user journey that started on the web.

Google Play

Android purchases and subscriptions complete the cross-platform picture for revenue.

See all integrations →
FAQ

Questions, answered directly.

Does Muon support iOS and Android?
Muon is designed around projects and events, so a project can include iOS and Android apps alongside a website and backend. Web is the first platform; iOS, Android and backend SDKs are planned.
Can I connect web and app journeys?
Yes. One project can span a website, an iOS app, an Android app and a backend service, with shared events — so a single user journey can move across platforms.
Which SDKs are planned?
Planned SDKs include JavaScript, Swift, Kotlin, Node.js, Python, Go and Rust. The Swift SDK is the reference template the other SDKs follow.
Can Muon track subscriptions?
Muon can connect subscription and revenue events through integrations such as RevenueCat, the App Store and Google Play, so app installs and subscriptions appear in the same journey as web and product events. See integrations →
Open source · self-hosted

One project for web, app and revenue.

Start with the web platform today, docker compose up, and grow into mobile as the SDKs land.