VirtuProbe Studio

The request manager
for people who break things.

One workbench for every wire-level protocol your stack actually speaks. Send a probe over HTTP, read the resulting email over IMAP, look up the user in LDAP — all in one chain. Built from scratch against the RFCs, so we can bend them when you need to.

Closed beta · seats limited HTTP · SMTP · IMAP · LDAP · more on the way Self-hostable · always

VirtuProbe Studio/Dashboard

server live · :8080

Real screenshot from the MVP build · UI 0.0.1-SNAPSHOT

A workbench, not a wrapper.

Three surfaces, one app. Probes for shaping a single request. Chains for stitching them together. A proxy that catches whatever's actually on the wire — and turns it into editable probes.

Probe editor

One protocol. One screen. Zero ceremony.

Method, URL, headers, body, response — all visible. Test variables resolve at send time so you can keep secrets out of the file. Status, latency, raw bytes; no chrome between you and the wire.

MITM proxy

Catch traffic. Save it as a probe.

Drop in the CA cert, point your client at :1080, watch every flow land in the table. Filter by host, status class, method. Promote any line to a saved probe — now it's part of your chain.

If it talks over a wire, you can probe it.

A Probe is one request on one protocol. A Chain is a flow of probes and iterators that pass data between each other. Mix protocols freely — fire an HTTP call, read the resulting email over IMAP, look the user up in LDAP, all in one runnable artefact.

Integration testing

End-to-end flows your CI can actually run.

The signup chain that touches HTTP, SMTP, IMAP and LDAP — captured once, replayable forever. No more bash glue between five tools.

Cross-protocol assertionsDid the API call land a verify email with the correct token within 30s?
Iterators & fixturesDrive a chain from a CSV, a vault, or another probe's response.
Reproducible artefactsEvery chain exports as a single file. Check it into the repo.

Security research

The unhappy paths most tools won't speak.

Implementations are written from scratch against the RFCs — so when you need to send something the spec forbids, the wire stays quiet and the bytes go out.

Hand-rolled stacksHTTP, SMTP, IMAP, LDAP — ours. Bend the protocol. The library won't push back.
Built-in MITMCaptured traffic lands as editable probes. Replay, mutate, fuzz, graph.
Chain libraryCurated probe packs for the work you keep doing twice.

Mail & identity infra

SMTP, IMAP, LDAP and SpamAssassin in one place.

Audit your mail server's edge cases without spinning up three CLI tools and a junk inbox. Score, bind, retrieve — all probes.

SMTP & IMAP probesSend malformed envelopes. Read what arrived. Diff against expectation.
LDAP queries & bindsHit your DC, assert directory state mid-chain.
SpamAssassin scoringScore any payload from the chain itself — regression-test deliverability.

Six tools that used to be five tabs.

Everything is the same primitive — a request, possibly chained, possibly intercepted, possibly scripted. Composability is the point.

Probes

One probe = one request, on one protocol. HTTP, SMTP, IMAP, LDAP today — with hand-rolled stacks so you can send what the spec forbids.

HTTP · SMTP · IMAP · LDAP · SpamAssassin

Chains

A chain is a flow of probes and iterators that pipe data between each other. Branch on response, fan out from a CSV, cross protocols freely.

HTTP → IMAP → HTTP → LDAP

MITM proxy

Intercept system-wide or scoped to a hostname. Captured traffic lands as editable probes — ready to replay, mutate, or fold into a chain.

listening · :8080 · TLS intercept on

Groovy scripting

One engine across pre/post-scripts, assertions, mutators and chain logic. The full JVM ecosystem is one import away.

vault.get("seed") · totp() · ctx.vars

Library

Curated probe packs and reference chains — OAuth flows, SMTP DSN edge cases, LDAP audits, spam-score regressions. Bring your own, share with team.

library · 412 chains · weekly drops

Shared workspaces

Live cursors, comments on probes, chain diffs. Roles per workspace. Self-host the API and UI servers when compliance asks.

2 collaborators · live

A chain is a graph of probes and iterators. Each step's output feeds the next via vault-scoped variables. Branch on response. Cross protocols freely. Replay anywhere — desktop, CI, or a self-hosted runner.

HTTP POST /v1/users · register extract $.id → vault.user

→

IMAP INBOX · FROM noreply@ extract token from body

→

HTTP PUT /v1/verify?t={{token}} assert 200 · verified

final step: LDAP bind to dc.target · assert cn=user in OU=Verified · exported as signup-flow.chain.vps

Self-hostable, always. Pick how much you want to split.

VirtuProbe Studio is a UI server, an API server and a UI client. Bundle them into one binary on your laptop, or split them across your network so the API runs where the targets actually are.

Standalone

Desktop app

Everything in one process. Open it, probe things, close it.

[ desktop app ] ├─ ui client ├─ ui server └─ api server

macOS, Linux, Windows
Local workspaces on disk
Zero infra to think about

Split UI / API

API where the targets are

Run the API server inside the network you're probing. UI on your laptop talks to it.

[ laptop ] [ dev env ] ui client → api server ↓ ↓ ui server targets

Probe internal services without VPN gymnastics
API runs as a daemon, container, or systemd unit
Client auth via mTLS or licence-issued tokens

Fully split

UI server, API server, clients

Three components, three machines. The team setup, with a shared workspace surface.

ui server ← ui clients (n) ↓ api server → targets

Shared workspaces, roles, audit log
Self-hosted licence server compatible
SSO-ready (OIDC, SAML on roadmap)

The request manager
for people who break things.

A workbench, not a wrapper.

One protocol. One screen. Zero ceremony.

Catch traffic. Save it as a probe.

If it talks over a wire, you can probe it.

End-to-end flows your CI can actually run.

The unhappy paths most tools won't speak.

SMTP, IMAP, LDAP and SpamAssassin in one place.

Six tools that used to be five tabs.

Probes

Chains

MITM proxy

Groovy scripting

Library

Shared workspaces

register → mail → verify → directory. One file.

Self-hostable, always. Pick how much you want to split.

Desktop app

API where the targets are

UI server, API server, clients

Get a seat in the closed beta.

The request managerfor people who break things.

A workbench, not a wrapper.

One protocol. One screen. Zero ceremony.

Catch traffic. Save it as a probe.

If it talks over a wire, you can probe it.

End-to-end flows your CI can actually run.

The unhappy paths most tools won't speak.

SMTP, IMAP, LDAP and SpamAssassin in one place.

Six tools that used to be five tabs.

Probes

Chains

MITM proxy

Groovy scripting

Library

Shared workspaces

register → mail → verify → directory. One file.

Self-hostable, always. Pick how much you want to split.

Desktop app

API where the targets are

UI server, API server, clients

Get a seat in the closed beta.

The request manager
for people who break things.