Deployport Machines

Yes. You install the agent on the Linux machines you already run. Connect your AWS or Google Cloud account for starting and stopping machines, firewall rules, volumes, backups and one-click restore. All of it works with nothing to connect if you provision the machine in one of our locations in US East or US West.

Then you create them with us. One click in the console or one command in your terminal gives you a machine in a Deployport datacenter with no cloud account to set up first. We run capacity on the East and West coasts of the United States with up to 32 GB of RAM and 8 cores per machine.

When you want Deployport to control a machine's power, firewall rules or backups, you create a trust role in your own account and revoke it whenever you like. You never hand over a key and it never needs administrator access. On AWS that is three EC2 operations for start and stop, two for firewall rules, and a handful of EBS calls for backups and restores.

Yes, and it works the same either way. Deployport reaches the machine over VIA Tunnels on Ubuntu so a box with no public address and no inbound ports open is as usable as one on a public IP. There is a native Cloudflare Tunnels integration if you already run those.

Absolutely. You tell us a machine is for development and it looks after itself from there. It stops when you are AFK and so does the bill. We give you an SSH command that works from your terminal or straight out of VS Code. Connecting is what starts it again so you never check whether it is running first. The desktop app on macOS and Windows gives you the same control when you would rather click than type.

Deployport only stops machines you configure to shut down when idle. You define the thresholds from SSH session count, CPU and network activity.

Literally anything you want. It is an ordinary virtual machine and it is yours.

Storage scales itself on AWS and Google Cloud. CPU and RAM are one click, at a time you choose. Deployport predicts when a volume will fill and scales automatically and smartly (AWS locks a volume for six hours after a resize. Grow it late or too small and you are stuck for the rest of the day, but not with us)

Yes. One volume on the machine is portable and replicates automatically. Put your work there and it moves with you: across cloud providers, or onto a server under your desk, a laptop, a Mac mini, a colocated box or your home lab.

Yes. Deployport connects to GitHub Actions over OIDC so no long-lived credentials sit in your repository. Our GitHub Action runs CLI commands directly in your workflow. That is all you need to launch a machine for a job and destroy it when the job is done.