Complex Stack vs
Simple Open-Source Analytics
PostHog is an all-in-one product platform with configurable privacy settings. Respectlytics is privacy-first by architecture with only 5 stored fields.
Quick Comparison
See the key differences at a glance
| Feature |
π¦
PostHog
|
Respectlytics
|
|---|---|---|
| Hosting Model |
π
Self-hosted or Cloud
You manage infrastructure
|
βοΈ
Managed SaaS or Self-Hosted
Free Community Edition available
|
| User Identifiers |
π
Auto-generated ID
$distinct_id persists across sessions
|
β
Never stored
By design
|
| Custom Properties |
β οΈ
Unlimited
PII leak risk
|
π‘οΈ
Not allowed
Minimized PII risk
|
| User Identification |
π
$distinct_id + properties
Persistent tracking
|
β
Session-based only
2-hour rotation
|
| IP Address Storage |
β οΈ
Stored by default
Can be disabled
|
β
Never stored
Transient geo only
|
| Mobile SDK Focus |
π±
Multi-platform
iOS, Android, Flutter, RN
|
π±
Mobile-first
Swift, Flutter, RN, Kotlin
|
| Conversion Intelligence |
π§
Manual funnels
Define yourself
|
π€
Automatic
Auto-discovered
|
| Setup Complexity |
βοΈ
Complex (self-host)
ClickHouse, Kafka, etc.
|
β‘
Simple
5-minute SDK setup
|
| Session Replay |
β
Built-in
Web + Mobile
|
β
Not included
Use dedicated tools
|
| Feature Flags |
β
Built-in
A/B testing included
|
β
Not included
Use dedicated tools
|
Self-Hosting Shouldn't Require a Platform Team
PostHog needs ClickHouse, Kafka, and Redis. Respectlytics needs PostgreSQL. Compare the real cost of self-hosting each.
PostHog Self-Hosted
Run your own analytics infrastructure
Infrastructure Requirements:
-
βοΈ
ClickHouse
Column database for analytics
-
βοΈ
Kafka
Event streaming
-
βοΈ
PostgreSQL
Metadata storage
-
βοΈ
Redis
Caching layer
Reality Check: Self-hosting requires dedicated DevOps, monitoring, backups, and security patches. The "free" option has significant hidden costs.
Respectlytics
Managed SaaS or self-hosted Community Edition
Two Deployment Options:
-
β
Managed SaaS
Zero DevOps. EU-hosted. Automated intelligence.
-
β
Self-Hosted (AGPL-3.0)
Free forever. Docker + PostgreSQL. Full source on GitHub.
-
β
Minimal infrastructure
Just Django + PostgreSQL. No ClickHouse, no Kafka, no Redis.
-
β‘
5-minute setup (either option)
Install SDK, start tracking
Open Source Advantage: Unlike PostHog's ClickHouse + Kafka stack, Respectlytics self-hosting requires only PostgreSQL. Same strict 5-field privacy architecture whether managed or self-hosted. Learn more about self-hosting β
Data Collection Differences
What each platform collects by default
PostHog
Default data collection
What PostHog Collects:
-
π
$distinct_id
Auto-generated, persists across sessions
-
β οΈ
IP Address
Stored by default ("Discard IP" option available)
-
π
Device Properties
Browser, device, location from IP
-
β οΈ
Custom Properties
UnlimitedβPII risk if not careful
Privacy Note: PostHog offers privacy controls including IP discarding, cookieless mode, and data masking. However, configuring these requires deliberate setupβthe defaults collect more data than Respectlytics.
Respectlytics
Strict 5-field schema
Only 5 Fields Stored:
-
β
event_name, timestamp
Core event data
-
β
platform
ios, android, web
-
β
country
Country-level only (IP discarded)
-
β‘
session_id
2-hour rotating, RAM-only in SDKs
Transparent & Defensible: The API rejects any request with extra fields. This makes it technically difficult to accidentally collect data you don't need.
π‘οΈ How Respectlytics Enforces Privacy
# Strict allowlist - only these 5 data fields are stored (plus app_key for auth)
STORED_FIELDS = frozenset({
'event_name', # Required
'timestamp', # Optional timing
'platform', # ios, android, web
'country', # 2-letter ISO code
'session_id', # 2-hour rotating, RAM-only
})
# API rejects any request with extra fields
if unexpected_fields := request_fields - ALLOWED_FIELDS:
raise PrivacyValidationError(
code="DISALLOWED_FIELDS",
reason=f"Custom fields not allowed: {unexpected_fields}"
)
Unlike PostHog's flexible schema, Respectlytics rejects any attempt to send extra data. This makes your analytics transparent and defensible by design.
When to Choose Each
Both platforms have their place. Here's our honest assessment.
π¦ Choose PostHog If:
- β’ You want an all-in-one platform (analytics, feature flags, A/B tests, session replay)
- β’ You have DevOps resources for self-hosted deployment (if data residency requires it)
- β’ You need session recordings and heatmaps alongside analytics
- β’ You're comfortable configuring privacy settings (IP discarding, cookieless mode)
- β’ You need to track individual user journeys across sessions and devices
Choose Respectlytics
If:
- β’ Privacy is a core valueβyou want to minimize data collection
- β’ You're building mobile-first (Swift, Flutter, React Native, Kotlin)
- β’ You want automated conversion insights without manual funnel setup
- β’ You want managed SaaS without DevOps β or free self-hosted Community Edition
- β’ You value transparent, defensible data practices over flexibility
Migrating from PostHog?
Switching is simpler than you think. Here's what changes.
π¦ PostHog Event
posthog.capture(
'purchase_completed',
{
$distinct_id: 'user_123',
$set: { email: 'user@...' },
price: 29.99,
product_id: 'SKU-456',
...
}
);
β Respectlytics Event
// Just the event name
// No user ID, no custom props
Respectlytics.track("purchase_completed")
// Privacy by design:
// - session_id rotates every 2 hours
// - No persistent user tracking
// - API rejects extra data
Migration Note: The shift from "track everything" to "track what matters" is intentional. You'll lose the ability to track individual users across sessionsβbut you'll gain defensible analytics with a minimal data surface. Consult your legal team for your specific requirements.
See also: Firebase vs Respectlytics β’ Mixpanel vs Respectlytics β’ Amplitude vs Respectlytics
Ready to Simplify Your Analytics?
Skip the DevOps headaches. Get privacy-first insights in 5 minutes.