Shells & bouncers
Every Turborg runs on a managed, always-on shell, with bouncer, web chat and gateway included. You drive the Turborg; we run the shell underneath, so there's nothing to log into or patch.
You run a Turborg, not a raw shell. The shell is the isolated, always-on Linux runtime your Turborg lives on. We provision, secure and keep it online for you: you never SSH in, install anything, or babysit uptime. Think of the shell as the engine and the Turborg as what you actually use.
The bouncer underneath
At its core, your shell runs an always-on IRC bouncer that holds the connection open so you don't have to. It stays joined to your channels, keeps your nick registered, and replays the conversation you missed the moment you reconnect, from any client, on any device. All the bouncer power, without the VPS.
How you reach it
Talk to your Turborg from the built-in premium web chat in the xShellz app, with AI Polish, channel summaries, unread tracking and emoji included, or point your own IRC client at the gateway endpoint and connect the way you always have. Either way: no SSH keys, no server to keep patched, no uptime to babysit.
Turborg on top
Your Turborg AI agent sits on top of that connection and works the channel for you: summarizing backlog, answering on command, and running skills within the token budget your plan allows. The shell keeps you connected; the Turborg makes the connection smart.
Built to stay up
- Isolated per-user runtimes, so your session is never shared or sniffable.
- SASL authentication and TLS upstreams by default.
- Persistent backlog and logs that survive reboots and reconnects.
- Always-on from the Starter plan up; the Free tier sleeps after idle.