What the Gateway does

The Gateway is the always-on hub of DevThrottle. Your coding agents do not run on it - they run in Directors on your own machines. What the Gateway does is hold the whole fleet's picture and keep it reachable: every Director dials out to it and keeps that connection open, and everything you do from anywhere else goes through it.

The gateway is the always-on hub

Think of the gateway as the meeting point. Your phone, a browser on another laptop, the Cockpit - they do not run agents themselves, and they never talk to your computers directly. They connect to the gateway, and the gateway reaches each session's Director over the connection that Director already opened outward. On a normal install nothing on your machine listens - the Director and the Launcher only dial out. A port (7878) is listened on only if you install the Gateway yourself on your own machine; the hosted Gateway involves no listener of yours at all.

Where the gateway can run

The gateway is a headless background service - there is no window to keep open - and the service itself is cross-platform. What differs is how you get it and run it:

• Windows. The download on this site. This is the path to take if you are hosting the gateway yourself on a machine you already leave on.
• Hosted by us. We run the gateway for you on Linux, so no machine of yours has to stay on at all. See pricing for the plans that include it.
• Linux, self-hosted. The gateway ships as a headless container image in the open source repository, so you can run your own on a Linux box or a server. There is no one-click installer for this yet - you build and run the image yourself.

A Mac is supported as a workstation: install the app on a Mac, run agents there, and connect to a gateway hosted elsewhere. A Mac cannot host the gateway today.

What lives on the gateway

• The fleet's picture. Session state and conversation history from every machine, so remote viewing and supervision work. The sessions themselves run in Directors on your computers.
• The source of truth. The gateway rules on which sessions are working, waiting on you, or done - which is why your phone, the Cockpit, and the desktop all agree.
• Scheduled runs. A built-in scheduler can launch unattended sessions on a cron schedule.
• The agent surface. The cc-devthrottle command line drives the fleet by talking to the gateway with the calling session's own key; the gateway reaches the owning Director down its outbound connection. The Director itself has no local listener, and no gateway connection means no agent tooling.

How your other devices connect

Because the gateway stays on, you do not have to be at any particular keyboard. Open the same sessions in a browser on any machine, or in your pocket on mobile. A session gets blocked while you are away - you answer it from your phone and keep the work moving. All of it goes through the one gateway that every Director reports to.

Where to go next

Ready to connect? Install DevThrottle and connect a gateway walks the whole path, including the wizard screen where you choose hosted, self-hosted, or not now. To see how the gateway fits with the rest of the pieces, read the core concepts.