tinyreplay

Spec sheet

Purpose

tinyreplay records browser sessions with a browser SDK, stores replay batches in local SQLite, and displays them in a local dashboard.Read 9 Oct 2026 · github.com

Audience

It is intended for indie developers and small teams inspecting browser sessions without adopting a full analytics platform.Read 9 Oct 2026 · github.com

Deployment

The project documents running from source or using its Docker image, with the SQLite data directory mounted for persistence.Read 9 Oct 2026 · github.com

Access controls

Dashboard Basic authentication and an ingestion token can be enabled through configuration, and the project advises using TLS and stronger access control via a reverse proxy before external exposure.Read 9 Oct 2026 · github.com

Captured data

The SDK records console and error messages plus network method, URL, status, and duration metadata; it does not read network bodies or headers, cookies, or browser storage aside from its session ID in sessionStorage.Read 9 Oct 2026 · github.com

Ingestion limits

The documented defaults are 100 ingest requests per minute per IP and a maximum request body of 5,000,000 bytes.Read 9 Oct 2026 · github.com

Integration

A browser SDK can be loaded as a server-served UMD bundle or installed as the @tinyreplay/sdk npm package.Read 9 Oct 2026 · github.com

License and support

The repository is MIT-licensed and directs security issue reports to a private channel described in its security policy.Read 9 Oct 2026 · github.com

Local storage

Session data is stored in a SQLite database, and retention is off by default unless RETENTION_DAYS is configured.Read 9 Oct 2026 · github.com

Maturity

tinyreplay is pre-1.0, and its APIs, storage format, configuration, and dashboard behavior may change before version 1.Read 9 Oct 2026 · github.com

Notable omissions

The project says it does not provide funnels, heatmaps, feature flags, user profiles, mobile SDKs, hosted storage, SSO, distributed ingestion, or compliance guarantees.Read 9 Oct 2026 · github.com

Privacy masking

Input masking is enabled by default, and marked elements can be masked or excluded before replay events are sent to the server.Read 9 Oct 2026 · github.com

Plans and prices

Every tinyreplay plan and price →

Where Specifiction places it

• Session Recording Software#28 of 307.4