Changelog

Bare metal & on-prem

Alien now installs and updates your product on bare metal and on-prem machines, yours or your customers'. You get releases, rollbacks, health, and logs for every machine, with no Ansible, SSH, or VPN.

Run one command on a machine and it joins the deployment:

On each machine
curl -fsSL 'https://pkg.alien.dev/acme/bare-metal-worker/install.sh?version=1.0.0' | sudo bash -s -- join --token 'aj1_…'

The token can be revoked from the dashboard. Machines connect out to Alien over HTTPS, so there's no inbound port, VPN, or SSH access to set up. Machines in the same deployment reach each other over an encrypted mesh.

Releases

Every alien release reaches every joined machine on its own. A release can go to a staging channel first, then to production. At Islo, a release is running in a median of 1.2 minutes.

When a release or a drain stops a process, the process gets up to the limit you set, as long as 24 hours, to finish its work.

Rollbacks

Roll back by promoting an earlier release. Its artifacts are reused, so nothing is rebuilt:

alien releases promote <release-id> --channel production

You can also pin one deployment to a known release while you debug.

Health and logs

Health, versions, and logs for every machine are in the dashboard, including machines behind a customer's firewall. If a machine loses its connection to Alien, it keeps running its last release.

What runs

Daemons run one process per machine, and can have full host access for hypervisors, network agents, and other software that needs the machine to itself. Stateless containers run alongside them. Each deployment gets its own domain, and Alien issues and renews the TLS certificates.

The same stack also deploys to AWS, Google Cloud, and Azure accounts, so moving a customer from their own machines to their cloud is a change of configuration.

In production at Islo

Islo runs agent computers on its own bare metal, in customers' AWS accounts, and on machines in customers' data centers, all from one release. A release reaches a machine in a median of 1.2 minutes, down from about eight with Ansible.

Read how Islo ships to all of them, why we built this in Bringing the web workflow to bare metal and on-prem, or start with the quickstart.