Replace Amplitude: self-hosted

▸Example Amplitude call (the "before")

js Respectlytics

import { Amplitude } from '@amplitude/analytics-react-native';

await Amplitude.init('YOUR_API_KEY', userId, {
  trackingOptions: { ipAddress: true, language: true, platform: true },
});

await Amplitude.identify({
  email: email,
  plan: 'pro',
});

await Amplitude.track('Paywall Purchase', { value: price, currency: 'USD' });

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

1
Remove the Amplitude SDK from your build (CocoaPods / SPM / Gradle / npm / pub)
2
Remove Amplitude.initialize(...) and track(...) call sites — replace with Respectlytics.configure() and Respectlytics.track("event_name")
3
Audit for Identify operation usage — those set per-user properties; remove them
4
If you used Amplitude Experiment for feature flags, plan a separate migration (e.g., GrowthBook or LaunchDarkly) — Respectlytics is analytics, not flagging
5
Confirm IDFA / AAID surfaces in your Info.plist + AndroidManifest are no longer needed by other SDKs before removing them

⇋Amplitude vs Respectlytics — self-hosted deployment

	Amplitude	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 Amplitude with self-hosted analytics