Replicata taps real production bytes in your own browser — LLM chat apps, real-time dashboards, collaborative editors — and replays them into your local renderer. Real chunk timing. Real SSE framing. Real edge cases. No mocks, no API keys, no cost.
$12/month · 7-day trial · cancel anytime
Open any streaming web app you already use in Chrome. Replicata observes the bytes in your own browser — passive tap, no automation, nothing sent anywhere.
Point Replicata at your localhost app. Real streams flow into your normal fetch("/api/chat") call. Your code doesn't know the difference.
Pair interactive elements. Type in real, your code reacts. Inject latency, disconnects, malformed chunks. Ship a renderer that handles production for real.
Mocks lie. They give you clean, uniform chunks on a predictable cadence. Real SSE streams are bursty, occasionally malformed, sometimes disconnect mid-message. Replicata makes the real ones your dev loop.
Replicata never automates the real app, never fires events into it, never scrapes or redistributes data. It's a DevTools-grade passive tap on your own browser session — you drive, it observes.
Shared, curated tag + endpoint libraries for the streaming apps you care about — updated as the apps change. Stop reverse-engineering selectors every month. Your subscription keeps you current.
Latency multipliers, mid-stream disconnects, dropped chunks, rate-limit responses, malformed JSON. Deterministic, replayable, offline. Your error UI finally gets tested.
7-day free trial, no card required
No. Replicata is a passive tap — it observes bytes in a browser you drive, just like the DevTools Network panel. No automation, no requests made on your behalf, no data ever leaves your machine. Treat it like a local debugger.
No. Your regular logged-in browser session is the source. Replicata watches what's already flowing and replays it into your renderer. Zero cost, zero keys.
~/.replicata/chrome-profile).Why user-launched Chrome? Because automation-launched browsers trip Cloudflare and similar bot checks. Your own Chrome session is indistinguishable from normal browsing — Replicata just observes what's already flowing.
Click through it in the Chrome window Replicata opened. It's the same challenge you'd see in any fresh browser session — Replicata doesn't bypass it. Once solved, the session persists; you won't see it again for a while.
Sign in normally in the Chrome window Replicata opened. Session lives in the dedicated profile and survives restarts — you won't need to re-auth unless the site invalidates the session itself.
Any. Replicata hands your app a normal Response from a normal fetch(). React, Svelte, Vue, vanilla — all the same.
Three. Laptop + desktop + work machine. Deactivate one to move to a new one.
macOS (Apple Silicon + Intel) and Linux x64 today. Windows coming soon.
Yes. One click in the Polar customer portal. Your license stays valid until the end of the paid period.
The 7-day trial is there to prevent unhappy paid customers. Email hello@replicata.dev if the trial didn't cover your case — we'll sort it out.