Replace GameAnalytics: self-hosted

▸Example GameAnalytics call (the "before")

swift Respectlytics

import GameAnalytics

GameAnalytics.configureBuild("1.0.0")
GameAnalytics.initialize(withGameKey: "YOUR_KEY", gameSecret: "YOUR_SECRET")

GameAnalytics.addProgressionEvent(
    withProgressionStatus: GAProgressionStatusComplete,
    progression01: "world_1",
    progression02: "level_5",
    score: 1200
)
GameAnalytics.addBusinessEvent(
    withCurrency: "USD",
    amount: Int32(priceInCents),
    itemType: "iap",
    itemId: sku,
    cartType: "main_paywall"
)

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

1
Remove pod 'GameAnalytics' from Podfile
2
Remove implementation 'com.gameanalytics.sdk:gameanalytics-android-sdk:...' from build.gradle
3
Remove GameAnalytics.initialize(...) and GameAnalytics.addBusinessEvent(...) call sites
4
Replace progression and resource event call sites with Respectlytics.track("event_name") using distinct event names per level / resource type
5
If you used GameAnalytics's benchmark comparisons as a product KPI, plan how you'll source those numbers post-migration

⇋GameAnalytics vs Respectlytics — self-hosted deployment

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