tinyreplay
tinyreplay.hane.studio
- Free plan
- Linux
- Web
- API
- Self-hosted
What tinyreplay is
tinyreplay is an open-source, self-hosted browser session replay tool for indie developers and small teams. A browser SDK records replay batches, stores them in local SQLite, and presents them in a local dashboard. Input masking is enabled by default, and marked elements can be masked or excluded before replay events are sent. 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 beyond its session ID in sessionStorage. Session retention is disabled unless RETENTION_DAYS is configured. The SDK can be served as a UMD bundle or installed as @tinyreplay/sdk. Deployment can run from source or Docker, with the SQLite directory mounted for persistence. Dashboard Basic authentication and an ingestion token are configurable. Defaults allow 100 ingest requests per minute per IP and a 5,000,000-byte request body. The project advises TLS and stronger reverse-proxy access controls before external exposure. It is MIT-licensed and pre-1.0, so APIs, storage, configuration, and dashboard behavior may change. It does not provide funnels, heatmaps, feature flags, profiles, mobile SDKs, hosted storage, SSO, distributed ingestion, or compliance guarantees.
Who it suits
tinyreplay fits indie developers and small teams wanting local browser-session inspection without a full analytics platform. It suits teams prepared to self-host and manage access controls.
Good to know, and what to watch
- Open-source MIT license
- Input masking enabled by default
- Stores sessions in local SQLite
- Supports source or Docker deployment
- Browser SDK offered as UMD or npm package
- Pre-1.0 behavior and formats may change
- No hosted storage or accounts
- No mobile SDKs or SSO
- No funnels or heatmaps
Plans
Every plan and priceOpen-source (self-hosted)
Open source
The verdict
tinyreplay keeps replay data self-hosted and exposes configurable masking, retention, and access controls. Its pre-1.0 status and missing analytics features matter when planning a broader product-analytics setup.
What the maker publishes
- 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. source
- Audience
- It is intended for indie developers and small teams inspecting browser sessions without adopting a full analytics platform. source
- 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. source
- Deployment
- The project documents running from source or using its Docker image, with the SQLite data directory mounted for persistence. source
- Ingestion limits
- The documented defaults are 100 ingest requests per minute per IP and a maximum request body of 5,000,000 bytes. source
- Integration
- A browser SDK can be loaded as a server-served UMD bundle or installed as the @tinyreplay/sdk npm package. source
- License and support
- The repository is MIT-licensed and directs security issue reports to a private channel described in its security policy. source
- Local storage
- Session data is stored in a SQLite database, and retention is off by default unless RETENTION_DAYS is configured. source
- Maturity
- tinyreplay is pre-1.0, and its APIs, storage format, configuration, and dashboard behavior may change before version 1. source
- 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. source
- Privacy masking
- Input masking is enabled by default, and marked elements can be masked or excluded before replay events are sent to the server. source
- Purpose
- tinyreplay records browser sessions with a browser SDK, stores replay batches in local SQLite, and displays them in a local dashboard. source
Checked against the maker's pages on 9 Oct 2026.