Replace mParticle: open-source

▸Example mParticle call (the "before")

swift Respectlytics

import mParticle_Apple_SDK
let options = MParticleOptions(key: "YOUR_KEY", secret: "YOUR_SECRET")
options.identifyRequest = MPIdentityApiRequest.withEmptyUser()
options.identifyRequest?.email = email
options.identifyRequest?.customerId = userId
MParticle.sharedInstance().start(with: options)
let event = MPEvent(name: "Paywall Purchase", type: .transaction)
event?.customAttributes = ["value": price, "currency": "USD"]
MParticle.sharedInstance().logEvent(event!)

Closed-source analytics SDKs require you to trust vendor claims about behaviour. Open-source SDKs let your security team verify those claims from source. For regulated industries this is often a procurement-gating requirement. Respectlytics's SDKs are MIT-licensed and fully open; the server is AGPL-3.0.

☑Remove mParticle cleanly

1
Remove the mParticle SDK from your build (mParticle-Apple-SDK / mparticle-android-sdk / react-native-mparticle / mparticle_flutter_sdk)
2
Remove MParticle.start() and MParticle.logEvent(...) call sites
3
Critically: review your mParticle output forwarders and decide which downstream destinations you still need data flowing to (most don't — Respectlytics is direct)
4
Delete Identity.identify() and modify() calls — those drive the identity merge graph
5
Delete the mParticle workspace's mobile input once events have stopped flowing

⇋mParticle vs Respectlytics — open-source sdk + server

mParticle	Respectlytics
SDK source publicly available	— see tool note above	Yes (MIT)
Server source publicly available	— typically no	Yes (AGPL-3.0)
Reproducible builds from source	— varies	Yes (CI publishes from same commit)
Fork-and-modify allowed	— varies by license	Yes
Public commit history	— typically no	Yes (GitHub)

❓Frequently asked questions

Where can we audit the source?

GitHub: github.com/respectlytics. Each SDK has its own repository with source, tests, CI configuration, and release tags. The server lives in a separate repo with the same conventions.

Are the published binaries reproducible from source?

Yes — CI builds use deterministic build commands. The artifacts published to CocoaPods / SPM / Maven Central / npm / pub.dev are produced by the same pipeline that runs against each commit. Reproducible builds are a goal we test against; report any discrepancy as an issue.

Can we modify the SDK and ship our fork?

Yes — MIT permits modification and redistribution with attribution. Many enterprises fork to adjust logging, add internal tracing, or vendor the SDK into their build.

Why MIT for SDK and AGPL for server?

Standard split for source-available SaaS (GitLab, Sentry, MinIO, Plausible). MIT on the SDK maximises consumer freedom — your app picks up the dependency without obligation. AGPL on the server prevents competing closed-source SaaS forks while allowing internal self-hosting freely.

⇢Related migration guides

Replace mParticle with an open-source analytics stack