Respectlytics Respect lytics
Menu
Replace Mixpanel Self-hosted deployment

Replace Mixpanel with self-hosted analytics

Migrate from Mixpanel to self-hosted Respectlytics. AGPL-3.0 server, MIT SDK. Helps developers avoid collecting personal data.

Example Mixpanel call (the "before")

swift Respectlytics
import Mixpanel

let mixpanel = Mixpanel.mainInstance()

// Identifies the user — distinct_id becomes joinable to email forever:
mixpanel.identify(distinctId: userId)
mixpanel.people.set(properties: [
    "$email": email,
    "$name": fullName,
    "plan": "pro",
])
mixpanel.track(event: "Paywall Purchase", properties: ["value": price])

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 Mixpanel cleanly

  1. 1

    Remove pod 'Mixpanel' from Podfile

  2. 2

    Remove implementation 'com.mixpanel.android:mixpanel-android:...' from build.gradle.kts

  3. 3

    Remove mixpanel-react-native from package.json or mixpanel_flutter: from pubspec.yaml

  4. 4

    Delete any Mixpanel.mainInstance().people.set(...) or identify() calls — those are the people-profile entry points

  5. 5

    Replace mixpanel.track(...) call sites with Respectlytics.track("event_name")

  6. 6

    Delete the Mixpanel project (or revoke the project token) in the Mixpanel admin once you've confirmed no more events arrive

  7. 7

    If you used Mixpanel-driven cohort exports for marketing, plan the cutover to whatever replaces those flows

Mixpanel vs Respectlytics — self-hosted deployment

MixpanelRespectlytics
Self-hostable— see tool note above (typically no)Yes (AGPL-3.0 server)
Operator-managed database— typically noYes (you choose Postgres deployment)
Air-gapped deployment possibleNoYes
SDK license— variesMIT (permissive)
Server license— typically closedAGPL-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.

Related migration guides

Track what matters. Collect nothing you don't.

Five-field event schema, RAM-only event queue, no IDFA, no AAID, no persistent user IDs. Helps developers avoid collecting personal data in the first place.