Inside your network. Callable from anywhere.
The systems that matter most are often the ones you cannot reach: an internal portal, a supplier extranet, a legacy admin screen on the far side of a VPN. Uplink gives them a front door without opening one in your firewall.
The agent dials out. Nothing dials in.
You run a Writ agent on a machine that can already reach the system — your laptop, a box in the office, a container in the same VPC. It opens one outbound HTTPS connection to Writ and keeps it. That is the whole network change.
- The agent connects outward to Writ and stays connected.
- A call to your published endpoint is handed down that existing connection.
- The workflow runs on your machine, against a system only it can see.
The page never leaves your network. The agent returns the result of the workflow — the rows you extracted, the confirmation you captured — and nothing else.
The three usual answers, and what they cost.
Every team that needs this has been offered the same three options. Uplink is the fourth.
Open a port
A firewall exception, an inbound rule, a public hostname, and a new thing on your attack surface — for one integration. Security review measured in weeks.
Build the API
Ask the vendor for one, or write a service against a system nobody wants to touch. Both are real projects with an owner and a budget.
Do it by hand
Someone logs in every morning, copies rows into a sheet, and the process stops when they are on holiday.
How many doors, and how hard you can knock.
A door is a published REST endpoint or MCP tool. The daily call ceiling is fair-use on the relay that carries traffic to your agent.
| Plan | Published doors | Relay calls / day |
|---|---|---|
| Open Source | 2 | 2,000 |
| Starter | 5 | 10,000 |
| Pro | 15 | 25,000 |
| Growth | 40 | 50,000 |
| Scale | 100 | 100,000 |
| Enterprise | Unlimited | 250,000 |
Runs dispatched to your own machine carry no compute charge on any plan, including the free tier. You are paying for the front door, never for the work behind it.
Two machines, one front door.
The same published endpoint can be served by our fleet or by your agent. Callers see one URL; you choose which side of the wall answers it.
What this required from your firewall: no inbound rule · no public hostname · no port opened
Nothing dials in. The agent holds one outbound connection, and the call rides back down it. There is no inbound rule to write and no port to open.
Your own machine — free, no account, runs while it’s awake; only the result leaves.
The agent dials out. Nothing dials in — a system behind your VPN becomes callable without opening a single inbound port. Local callers can stay entirely local; add Uplink only when a remote caller needs to reach a workflow behind your firewall.
Questions people actually ask
Do I have to open a firewall port?
What actually leaves my network?
What does it cost to run?
Can I self-host the whole thing?
What happens if the agent is offline?
Give your internal system a front door.
Free on your own hardware, forever. No inbound port, no public IP.