Run and simulate API, service and agent calls against any environment — in an isolated sandbox, with built-in APM tracing, and without writing to the real database.
macOS (Apple Silicon & Intel) · Windows · works against your existing Sterling runtimes
Everything you'd reach for on a support case, a config change, or a tricky debug — in one window.
APIs, services/flows and agents — run them exactly as the platform would, against the real config, and read the response inline.
Every probe runs in its own write overlay and journal. Reads hit the live system; writes never touch the real database.
See the call tree, SQL, timings and async fan-out for each run — the slow query or the extra hop, right where it happened.
Point it at each of your runtimes — dev, QA, preprod, prod. The API catalog and config come live from that install.
Nothing is deployed into Sterling. Loupe drives your runtime from your laptop — read the jars where they are.
Keep several probes open, name them, re-run them. Each one freezes with exactly the request it sent and the result it got.
No server changes, no staging data — point it at a runtime and go.
Add an environment with its Sterling runtime directory and login. Loupe reads the API catalog and config straight from it.
Pick an API, service or agent, give it input, and simulate. It runs in a sandbox — reads are real, writes are captured.
See the response, the SQL, the call tree and timings. Tweak and re-run until you understand it.
One license covers your active devices; manage seats any time. (Launch pricing — adjustable.)
Grab a build and activate with your Customer ID and license token.
The app isn't code-signed yet, so your OS shows a one-time security prompt:
macOS — unzip (double-click the .zip), then open Terminal and run:
xattr -cr ~/Downloads/Loupe.app…then double-click Loupe.app. (One time only.)
Windows — run the .exe and click More info → Run anyway.
No. Each probe runs in an isolated sandbox: reads go to the live system, but writes are captured in a per-probe overlay and journal and never committed to the real database.
No. Loupe runs on your laptop and drives your existing Sterling runtime directory. Nothing is deployed into the OMS server.
macOS (Apple Silicon and Intel) and Windows.
A license is per-seat. Your activation enrolls your device; an admin can manage seats and devices at any time. Licenses are delivered securely and verified at startup.
Reach out and we'll get you set up with an evaluation.