Deployport Machines

Yes, we provision virtual machines where you have full control of. We run hosting 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 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.

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.

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 offers two profiles: Development and Production. Production machines never stop when idle. Only Development machines shut down when idle, and you define the thresholds for 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. 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.