Syncline · House #11,653

What it is

Calls itself “Session replay”.

• Calls itself: Session replay

“Session replay records what a person is looking at.”

Where it puts itself

Rules out “Retention”.

• Says it will not: Retention

“The interesting part is not either half — both exist already — but the seam between them, and how it is made reliable.”

“Retention is not implemented. Nothing expires or is deleted automatically, and there is no per-user deletion endpoint.”

What it costs

A free tier, free forever.

• Free plan: free forever

“Open source · self-hosted · AGPL-3.0”

Who it sells to

Sells to developers.

• Sells to: developers

“There is no Syncline backend SDK, and there should not be one. Syncline is a plain OTLP sink: if your services already emit OpenTelemetry, the integration is two environment variables.”

How it runs

A web app. Can be self-hosted. Offers an API. Open source.

• Kind: web
• Runs where: self-hosted
• API: yes
• Open source: yes

“…syncline-browser records the session with rrweb”

“Syncline is self-hosted; recordings never leave your infrastructure.”

What it works with

Integrates with OpenTelemetry and rrweb. Names GitHub, Google and 3 more on its pages.

• Integrates with: OpenTelemetry · rrweb
• Names: GitHub · Google · MinIO · +2

“Google, GitHub and GitLab are available on top of that”

“Docker for Postgres, Redis and MinIO.”

What it offers as proof

In beta. Instant signup. Publishes docs.

• Stage: beta
• Instant signup: yes

“Pre-alpha. Recordings are scoped to the organization that owns them and the dashboard requires an account, but there are still no invitations, no roles beyond owner and member, and no retention or deletion. Do not point this at production traffic yet.”

“Sign in Get started”