Product5 min read
One URL for your terminal, editor and files: how the gateway works
The dashboard, the editor, the terminal, and the file manager all live behind a single address.
You get one link to your machine, and behind it is everything: the dashboard, the editor at /code/, the file manager at /files/, the terminal, and the workspace. That is the gateway's whole job — to be the single address that all the tools live under.
One URL, many tools
Each tool is a separate program on the machine, but you never have to know their individual ports or hostnames. The gateway maps a clean path to each one, so moving from your editor to a terminal to your files is a matter of paths under a single origin.
No second password
Because the backends are not exposed on their own, the gateway is the only thing that authenticates you. Sign in once and every tile on the dashboard opens without asking again. The convenience and the security are the same fact seen from two sides.
Why one origin matters
Living under one address is also what makes the machine feel like a single place rather than a bag of services. You bookmark one link. You share one link. And the machine underneath can change how it is wired without changing the address you use.
More posts
Product5 min read
Persistent VM vs. ephemeral container for coding agents
A machine that remembers what you were doing is a different tool from one that resets every session.
Product4 min read
Which region should your dev machine be in? Europe, US or Asia
Pick by the two things that actually change: how far the packets travel, and where the data sits.
Product5 min read
Is it safe to run a coding agent on a cloud VM?
Every tool binds to localhost with its own login switched off. The gateway is the only way in.