tungent
For agents and the people who run them

The tunnel that doesn't rot.

One command gives a local port a stable HTTPS hostname, its own credentials and an audit trail. No account, no dashboard tour, no expiry clock.

Free to start. The hostname you get today still works next month.

Three commands, then it is just a URL

  1. 1

    Run it next to your service

    curl -fsSL https://app.dev.tungent.ai/cli/install.sh | sh
    tungent up 3000

    Nothing to sign up for. The CLI makes a device key, and that key is your identity. (npm i -g tungent once it is published.)

  2. 2

    Get a hostname and credentials

    https://my-app-witty-island-c54a.tungent.ai
    user: witty-island-c54a  password: …

    Reachable straight away. Add a password when you want one, and waive it on the paths a webhook or an OAuth callback needs.

  3. 3

    Claim it whenever you like

    tungent claim

    Keep working first and attach it to an account later. Every address you have already handed out keeps working, whether you simply claim it or fold it into an account you already have. Nothing you gave a colleague, a webhook or an OAuth config has to be changed.

Built for things that must stay reachable

The name is yours to keep

Hostnames, credentials and settings are kept while your connector is away and returned unchanged when it comes back — no rotating URL to chase, and nothing to re-send to whoever you gave it to. An idle tunnel stops serving after two hours and resumes under the same name; --persistent keeps it live indefinitely.

Two ways in, one identity

Start with a plain ssh -R and install nothing at all. Switch to the connector when one port is not enough: your machine gets an address on our side, so several services can be published at once. The same device key backs both, so switching costs nothing and re-registers nothing.

Survives our restarts

Connectors reconnect on their own, and re-establish themselves after a restart without being told. A deploy on our side is not an outage on yours.

Open when you want it, closed when you don't

An endpoint is reachable the moment it exists, so a demo link just works. Ask for a password and you get one, minted for that endpoint, with the option to waive it on the paths a webhook or an OAuth callback needs.

Made for agents

A REST call does what the CLI does, and returns the URL, the credentials and an audit link in one response. Agents do not have to read a dashboard.

You can see the traffic

Per-endpoint bandwidth, live status and an audit of what was opened and by which device, in the dashboard and over the API.

What it costs

Free is 10 endpoints, with no card and no trial clock: 1 GB of traffic a month before you have an account, 2 GB once you claim the workspace. Paid plans start at $4 and raise the traffic, not the rules.