/ SONDA · AUTOMATE

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.

NO AGENT NO LOCAL PORT TLS INSIDE THE CHANNEL KNOWN_HOSTS HONOURED

How it works

ChannelEach request is one direct-tcpip channel over the SSH login — like ssh -L without the port. Parallel sends share the login; nothing stays connected between them.
TLSRuns end to end inside the channel, with the request's own verify switch and the Network page's CAs and client certificates. The destination's SNI is preserved.
LoginA key file with an optional passphrase, a password (keyboard-interactive answered), or the SSH agent — on Windows the OpenSSH agent's named pipe.
Host key~/.ssh/known_hosts first. An unknown host is a first contact: the fingerprint shown, accepted, appended. A changed key is refused, with no override in the app.
ScopeHTTP requests, GraphQL introspection and OAuth token fetches, and a load test's origins. Inherited from a folder or a project, overridable back to Local.
/ WHERE THE CALL LEAVES FROM

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 tunnels
/ IN USE

Pick 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.

# tunnel · bastion · deploy@bastion.example.com · SSH agent Test the tunnel reach api.example.com from the server Logged in to bastion.example.com as deploy in 212 ms; api.example.com:443 answered the server in 9 ms hung up — nothing kept connected Connect ● connected to bastion.example.com as deploy since 09:12 · 48 requests · 1.4 MB keepalive every 30 s · dropped after 45 s without an answer # on the answer 200 OK · 142 ms via bastion # made from bastion.example.com # the day the server's key changed the key of bastion.example.com has CHANGED — refused # no override in the app
TestLogs in and optionally reaches a host and port from the server, reporting the login and the reach in milliseconds. Nothing stays connected.
StatusConnected or not, the host key, the requests carried, the bytes, the last error. A chip on the answer says it was made from this server, through this tunnel.
TravelsThe server, the port and the accepted host key travel with the project.
StaysThe login — user, key, password — stays on each computer. Passwords and passphrases are masked, blank in exports, never echoed in errors.
/ LOCKFLARE SONDA

Via, in the free edition.

Via, listed →