Full control.
Down to the details.

Execute commands, read and write files, and stream output from a running machine. Control the environment directly from your backend or agent.

Enable SSH and connect with your own terminal or development tools. Install packages, inspect processes, and work directly inside your VM.

Open a graphical desktop in your browser or connect through VNC on a supported image. Desktop availability and capabilities depend on the image.

Use the dashboard to browse and edit your machine’s files, or read and write them through the Runtime API. Your tools and automation work with the same filesystem.

Control your Linux environment with root access. Install packages, compile code, and run the services your project needs within its allocated resources.

Choose a prepared OS or application image from the catalog, or use a public Docker image as the base for a Linux VM. Image requirements and capabilities vary.

Create directed private links and open specific service ports. Inbound connections start closed, including between your own VMs; runtime API calls still require authentication.

Expose an application port and get a managed HTTPS URL. Public access is opt-in, and the app must listen on the exposed port inside your VM.

Connect your domain to a VM’s service. Point your DNS to the edge and let the platform provision TLS for the configured route.

Run named background processes with start and stop controls, restart policies, and streamed logs. Workload logs have configurable, bounded retention.

Share a VM, namespace, or account with collaborators using their own logins. Choose Viewer, Developer, or Manager access; Developer and Manager roles include runtime access.

Scope API credentials to the resources and permissions an integration needs. Keep automation access separate from a teammate’s personal login.

A normal VM stop retains its writable disk so files remain available on the next start. Live process memory is not retained by a stop; retained storage remains billable.

Set a time to live for short tasks, tests, or sessions. Choose to stop, pause, or remove the VM at expiry, and extend the lifetime while it is still needed.

Compatible persistent Linux VMs can save memory and release running compute while idle. A request to the exposed web app wakes the same VM, subject to available capacity and credit.

Create a versioned, disk-only archive for backup and restore. Archives are separate from memory snapshots, which preserve a supported VM’s execution state.

Divide a purchased CPU, RAM, and storage pool across one or many VMs. Account limits, retained disks, image requirements, and per-VM limits still apply.

Review management actions, their actor, and their outcome across machines. Audit history records lifecycle and configuration changes, not terminal keystrokes or file contents.