Replace Amplitude: open-source

Q: Where can we audit the source?

GitHub: `github.com/respectlytics`. Each SDK has its own repository with source, tests, CI configuration, and release tags. The server lives in a separate repo with the same conventions.

▸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' });

Closed-source analytics SDKs require you to trust vendor claims about behaviour. Open-source SDKs let your security team verify those claims from source. For regulated industries this is often a procurement-gating requirement. Respectlytics's SDKs are MIT-licensed and fully open; the server is AGPL-3.0.

☑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 — open-source sdk + server

	Amplitude	Respectlytics
SDK source publicly available	— see tool note above	Yes (MIT)
Server source publicly available	— typically no	Yes (AGPL-3.0)
Reproducible builds from source	— varies	Yes (CI publishes from same commit)
Fork-and-modify allowed	— varies by license	Yes
Public commit history	— typically no	Yes (GitHub)

❓Frequently asked questions

Where can we audit the source?

GitHub: github.com/respectlytics. Each SDK has its own repository with source, tests, CI configuration, and release tags. The server lives in a separate repo with the same conventions.

Are the published binaries reproducible from source?

Yes — CI builds use deterministic build commands. The artifacts published to CocoaPods / SPM / Maven Central / npm / pub.dev are produced by the same pipeline that runs against each commit. Reproducible builds are a goal we test against; report any discrepancy as an issue.

Can we modify the SDK and ship our fork?

Yes — MIT permits modification and redistribution with attribution. Many enterprises fork to adjust logging, add internal tracing, or vendor the SDK into their build.

Why MIT for SDK and AGPL for server?

Standard split for source-available SaaS (GitLab, Sentry, MinIO, Plausible). MIT on the SDK maximises consumer freedom — your app picks up the dependency without obligation. AGPL on the server prevents competing closed-source SaaS forks while allowing internal self-hosting freely.

⇢Related migration guides

Replace Amplitude with an open-source analytics stack