Deployport Machines

Yes. Deployport Compute runs on the East and West coasts of the United States, with up to 8 cores and 32 GB of RAM per machine, and you have full control of it.

When you want to use Deployport with AWS and GCP, 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.

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.

No. A Production Machine never powers off on its own, and an Auto-Stop Machine stops only when it is idle. You set what counts as idle: SSH sessions, CPU and network activity.

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

Storage grows before it fills, on AWS and Google Cloud. Deployport predicts when a volume is running out and grows it for you, so you never wait out the six-hour lock AWS puts on a resized volume. CPU and RAM are one click, whenever you choose.

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.