Every request your app makes, on the record.
A capture layer built into every session — manual or automated — records your app's HTTP and HTTPS traffic as it happens. No proxy setup ritual, no separate tool: connect to a device and the recording has already started.
Recording starts when the session does.
Capture starts the moment a session connects — manual or automated. Testers watch requests appear live while they drive the device; afterwards, anyone can pull the traffic for exactly the time range they care about.
- Auto-start on session connect — nothing to switch on
- Live request view in the session, alongside the performance vitals recorded on the same timeline
- HAR download, time-ranged, per session or per test result
- Traffic attached to results, so a failing test carries its own network evidence
HTTPS and gRPC, readable.
HTTPS decryption
The lab-managed proxy decrypts your app's TLS traffic for inspection — inside your network, under your control. Headers, bodies, timings, and status codes, not just hostnames.
Protobuf decoding
Binary gRPC and protobuf payloads decode into readable messages using your proto descriptors — so API traffic that other tools show as opaque bytes reads like JSON here.
Test the failure your backend won't give you.
Reproducing a 500, a malformed payload, or a slow edge case usually means begging another team to break staging. The traffic modifier does it at the proxy instead — per session, without touching any server.
Rewrite rules
Change status codes, headers, or bodies on matching requests or responses.
Map Local
Serve a local or inline file as the response — a mock endpoint with no mock server.
Breakpoints
Pause a request mid-flight, edit it by hand, and resume — or abort it.
Team presets
Save rule sets to a shared library so the whole team reproduces the same conditions.
Your staging is already reachable.
Cloud device farms make you tunnel out to reach anything internal. RobusTest devices sit on your LAN — staging environments, internal APIs, and service meshes are reachable the way they are from any machine in the office.
- Devices on your network — internal hostnames resolve natively
- Secure tunnels for nodes in other offices or labs behind NAT
- Per-session WiFi switching to test against different network segments
See what your app says on the wire.
Bring a build to a demo session and watch its traffic captured live — then take the HAR file with you.