Replace Kochava: self-hosted

▸Example Kochava call (the "before")

swift Respectlytics

import KochavaTracker

KochavaTracker.shared.registerWithAppGUID("YOUR_APP_GUID")

let event = KochavaEvent(eventTypeEnum: .purchase)
event.appStoreReceiptBase64EncodedString = receiptBase64
event.priceDoubleNumber = NSNumber(value: price)
event.currencyString = "USD"
event.userIdString = userId
KochavaTracker.shared.send(event: 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 Kochava cleanly

1
Remove pod 'KochavaTracker' from Podfile
2
Remove implementation 'com.kochava.tracker:tracker:...' from build.gradle
3
Remove react-native-kochava-tracker from package.json if used
4
Remove KochavaTracker.shared.registerWithAppGUID(...) and sendEvent(...) call sites
5
Remove NSUserTrackingUsageDescription from Info.plist if Kochava was the only ATT-needing SDK
6
Remove AD_ID permission from the merged Android manifest if no remaining SDK contributes it

⇋Kochava vs Respectlytics — self-hosted deployment

	Kochava	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 Kochava: no att prompt Same tool, No ATT prompt Replace Kochava: no pii collected Same tool, No PII collected Replace Kochava: no phi collected Same tool, No PHI collected Replace Kochava: 5-field event schema Same tool, 5-field event schema Replace Kochava: ram-only event queue Same tool, RAM-only event queue Replace Kochava: fewer third-party sdks Same tool, Fewer third-party SDKs Replace Kochava: smaller app binary Same tool, Smaller app binary Replace Kochava: faster cold start Same tool, Faster cold start Replace Kochava: eu data residency Same tool, EU data residency Replace Kochava: 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 Kochava with self-hosted analytics