Respectlytics Respect lytics
Menu
βš–οΈ Comparison Guide

Self-Hosted vs
Privacy-First SaaS

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 Respectlytics
Hosting Model
🏠 Self-hosted or Cloud You manage infrastructure
☁️ Managed SaaS No DevOps burden
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: The Hidden Costs

PostHog's self-hosting is powerful, but comes with operational overhead

πŸ¦”

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

Respectlytics

Fully managed, privacy-first

What You Get:

  • βœ…
    Zero DevOps

    We handle infrastructure

  • βœ…
    Auto-scaling

    Handles traffic spikes

  • βœ…
    Minimal data by default

    Strict 5-field schema

  • ⚑
    5-minute setup

    Install SDK, get insights

Focus on Your Product: No infrastructure to manage, no security patches, no ClickHouse tuning. Just analytics that respects privacy. Need on-premise? Enterprise plans include self-hosted deployment.

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

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

analytics/privacy_guards.py
# 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

Respectlytics 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 on-premise for Enterprise
  • β€’ You value transparent, defensible data practices over flexibility

Migrating from PostHog?

Switching is simpler than you think. Here's what changes.

πŸ¦” PostHog Event

posthog-event.js
posthog.capture(
  'purchase_completed',
  {
    $distinct_id: 'user_123',
    $set: { email: 'user@...' },
    price: 29.99,
    product_id: 'SKU-456',
    ...
  }
);

βœ“ Respectlytics Event

respectlytics-event.swift
// 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.

Ready to Simplify Your Analytics?

Skip the DevOps headaches. Get privacy-first insights in 5 minutes.