The Ruust CLI · Open source

Your nest,
from the terminal.

Deploy, tail logs and drive your whole platform without leaving the shell. One static binary, browser login, and the same flat-priced Eggs.

brew install · browser login · single binary

One binary, whole platform

Drive Ruust from the shell.

ruust · ~/aurora
~ $ brew install ruustrun/tap/ruust
→ installed ruust · one static binary
~ $ ruust login
authorised in the browser · signed in
~ $ ruust deploy
hatched · live at https://aurora.eu-west.ruust.run
What it does

Everything the panel does, in your shell.

ruust login

Browser login, no tokens

Sign in through your browser over a loopback callback. Nothing to paste, no long-lived API key to leak into your shell history or a dotfile.

ruust deploy

Deploy from the terminal

Push and hatch an Egg without leaving the shell. Watch it build, pass its health check and go live, then jump straight to its URL with ruust open.

ruust logs -f

Live logs and status

Stream an Egg’s logs in real time. ruust list and ruust status show your whole nest at a glance, so you never open a browser to check on things.

ruust shell

A shell in your container

Drop into a running Egg like docker exec -it, a real terminal over a secure relay. Poke at the filesystem, run a one-off script, or open psql on a database Egg, all without SSH keys or a bastion.

brew install

One static binary, open source

Homebrew or a single download, no runtime to install. The CLI is Apache-2.0 and developed in the open, so you can read every line before you run it.

Install

Two lines to your first deploy.

$brew install ruustrun/tap/ruust
$ruust login

Prefer not to use Homebrew? Grab the single binary for your platform from the releases page. Then run ruust deploy from any repo.

Stay in the terminal

Ship without leaving the shell.

Install the CLI, sign in through your browser, and deploy your first Egg in a couple of commands. Open source, one binary, no keys to paste.