▸Example mParticle call (the "before")
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!)Regulated industries — telehealth, fintech, government, defence — frequently require that analytics data never leave operator-controlled infrastructure. Respectlytics's self-hosted option (AGPL-3.0 server + MIT-licensed SDKs) lets you run the entire analytics stack on your own hardware. The SDK is the same; only the API endpoint changes.
☑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()andMParticle.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()andmodify()calls — those drive the identity merge graph -
5
Delete the mParticle workspace's mobile input once events have stopped flowing
⇋mParticle vs Respectlytics — self-hosted deployment
| mParticle | Respectlytics | |
|---|---|---|
| Self-hostable | — see tool note above (typically no) | Yes (AGPL-3.0 server) |
| Operator-managed database | — typically no | Yes (you choose Postgres deployment) |
| Air-gapped deployment possible | No | Yes |
| SDK license | — varies | MIT (permissive) |
| Server license | — typically closed | AGPL-3.0 (source-available) |
❓Frequently asked questions
What's the AGPL-3.0 obligation in practice?
If you modify the server source AND offer the modified server as a service to third parties over a network, you must publish your modifications under the same license. Internal self-hosting for your own apps does NOT trigger publication obligations. Consult your legal team for specific applicability.
What infrastructure do we need?
A Linux host (or container) running Python 3.12 + Postgres 14+ + a reverse proxy (nginx / Caddy). The default configuration scales to ~10 million events/day on a 4-vCPU / 8 GB box; larger deployments scale horizontally. See the public README for hardware sizing guidance.
Do we get updates automatically?
No — self-hosted deploys pull the latest source and run migrations on a cadence you control. We publish release notes for each version. No auto-update; you decide when to upgrade.
Are the SDKs AGPL too?
No — SDKs are MIT-licensed. Fork and modify freely with no copyleft obligation. Only the server is AGPL.