mrokiSafe shadow traffic testing for production systems.
Mirror real production traffic to a shadow copy of your service. mroki diffs the JSON responses and shows every field that drifted, before a single user is affected.
How it works
What happens to every request mroki mirrors.
Live traffic comes first
Your users always get the live response. Shadow mirroring runs to the side and never delays or breaks production — every diff, API call, and error stays best-effort.
Diffing lives in the API
mroki-api diffs the two responses and stores each change as an RFC 6902 patch. Re-diff later with new rules — no replay needed.
See what changed
Read live and shadow responses side by side in the hub, with changed fields highlighted and a diff rate showing how often they disagree.
Self-hosted & open source
Everything runs on your own infrastructure. No traffic leaves your network, no account to create, MIT-licensed.
Live vs shadow, field by field.
Every mirrored request becomes a diff you can read three ways — side by side, inline, or as a list of exact changes.
Live and shadow side by side, with changed fields highlighted.
- Added
- Removed
- Replaced
See how your change behaves on real traffic.
Bring up the full stack with one Docker Compose file, point a gate at your live and shadow services, and start comparing.