Tunnels for real domains

Ship local services through real domains.

Private access, streaming responses, and per-route timeouts in front of anything running on your laptop.

relay.tuniq.dev

active route

admin.acme.com

/ -> 127.0.0.1:30380

internet

request

relay

policy

desktop

loopback

state

private

latency

42ms

transfer

128 MB

Route policy lives in the cloud. Traffic stays on the tunnel.

A route resolves host and path to an enrolled desktop agent and a high local port. The relay enforces access and timeout policy before forwarding across the agent socket.

Route ownership

Domains, tuniq.dev subdomains, and path prefixes live in one control plane.

Boundary access

Private routes require bearer tokens at the relay before traffic touches localhost.

Streaming transport

SSE, downloads, chunked responses, and long polling stream after first byte.

Desktop control

The agent keeps an outbound relay socket and exposes a local MCP control surface.

Private tunnels without app changes.

SHA-256 token hashes in the database
One-time reveal when tokens are created
Relay strips Authorization before forwarding
Audit log records token and billing changes

example request

curl -H "Authorization: Bearer <token>" \
  https://admin.acme.com/

relay:
  resolve route
  verify bearer
  forward to 127.0.0.1:30380

Free

Public tuniq.dev tunnels for demos, prototypes, and short-lived previews.

1 GB

monthly transfer included

Pro

Custom domains, private route tokens, uncapped transfer, and 10 minute first-byte timeouts.

10m

route timeout ceiling