Replace Branch: self-hosted

▸Example Branch call (the "before")

swift Respectlytics

import BranchSDK

Branch.getInstance().initSession(launchOptions: launchOptions) { params, error in
    // Branch fingerprint + IDFA matching happens here.
    if let referringLink = params?["~referring_link"] as? String {
        // Route the user based on the deep link...
    }
}

Branch.getInstance().userCompletedAction("Paywall Purchase", withState: [
    BranchStandardEventTransactionId: orderId,
    "revenue": 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 Branch cleanly

1
Remove Branch from your build (Branch / io.branch.sdk.android:library / react-native-branch / flutter_branch_sdk)
2
Remove Branch.getInstance().initSession(...) and userCompletedAction(...) call sites
3
Decide what replaces Branch's deep-link routing — Universal Links + App Links are first-party alternatives (no SDK; OS-handled)
4
Remove Branch URL schemes from your Info.plist and AndroidManifest.xml
5
Delete the Branch app dashboard entry once events stop flowing

⇋Branch vs Respectlytics — self-hosted deployment

	Branch	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.

⇢Related migration guides

Replace Branch: no att prompt Same tool, No ATT prompt Replace Branch: no pii collected Same tool, No PII collected Replace Branch: no phi collected Same tool, No PHI collected Replace Branch: 5-field event schema Same tool, 5-field event schema Replace Branch: ram-only event queue Same tool, RAM-only event queue Replace Branch: fewer third-party sdks Same tool, Fewer third-party SDKs Replace Branch: smaller app binary Same tool, Smaller app binary Replace Branch: faster cold start Same tool, Faster cold start Replace Branch: eu data residency Same tool, EU data residency Replace Branch: open-source sdk + server Same tool, Open-source SDK + server Replace Firebase Analytics: self-hosted deployment Same outcome, Firebase Analytics Replace Google Analytics for Firebase: self-hosted deployment Same outcome, Google Analytics for Firebase

Replace Branch with self-hosted analytics