Send from where the API can be reached.
The API only answers the bastion's address. The staging network is private. The partner whitelisted one server. Via makes the request from that server: a tunnel item is an SSH login Sonda holds open, a request picks it next to Send, and the call leaves from there — with nothing installed on the box and no port opened on yours.
How it works
The address stays the real one. The request leaves from the server.
A request picks a tunnel under Via, next to Send — or its folder or its project does, and everything inside rides it, while a single request can still say Local. Each send is one direct-tcpip channel over the SSH login Sonda holds open: like ssh -L, without the port. TLS runs end to end inside the channel, with the request's own verify switch and the Network page's CAs and client certificates, and the destination's SNI preserved. Parallel sends share the login; nothing stays connected between them.
Before any of it, the server's key. ~/.ssh/known_hosts first; a host not met yet is a first contact — the fingerprint shown, accepted, appended; a changed key is refused, with no override in the app. Nothing is installed on the box, and no port is opened on yours. It carries HTTP requests, GraphQL introspection and OAuth token fetches, and a load test's origins.
Load tests from tunnelsPick it, test it, share the server but not the login.
A tunnel connects on demand, at Send. A keepalive every 30 seconds; dropped after 45 without an answer, with the reason shown. Test it before anything rides it: it logs in, reaches a host and port from the server if you name one, says both in milliseconds, and hangs up.
Beside it, one tunnel tested, connected and carrying requests — and the same server the day its key changed.