​
Overview

Compute is where your machines live and where you shape how they run.
Navigation: Compute. The group expands to the screens below.

​
Screens in this area

​
Virtual Machines

The list is your inventory of instances. Click a machine to open its detail page, which is where you act on an individual VM — starting and stopping it, resizing it, attaching storage and networking, and cloning or destroying it. Creating a machine walks you through naming it, choosing a zone, picking a boot source (a template or ISO), selecting a compute offering for vCPU and memory, sizing its disk, and optionally attaching an SSH key.
If your account has no region yet, the create flow first sets up a region, VPC, and network. This is expected on a new account — see the Quickstart.
Creation is asynchronous. The machine appears in the list in a provisioning state and becomes usable when its job completes.
Inside the create form, the SSH key rows offer view public key, copy key, and rename actions that are not yet available — they’re present but do nothing. Manage keys from the SSH Keys screen instead.

​
Reaching a new machine

A new VM has a private address only. To make it reachable you acquire a public IP, enable Static NAT to the machine, and open the ports you need in Firewall Policies.
Static NAT is the only inbound service in the current phase — load balancing and port forwarding are both switched off. One public IP maps to one machine.

​
SSH Keys

Register the public half of an SSH key pair here, then attach it to machines as you create them. Simnet never holds your private key.
Register your key before creating your first machine. Attaching a key at create time is straightforward; getting into a machine that was built without one is not.

​
Affinity Groups

Affinity groups express placement intent — keep these machines apart so a single host failure can’t take them all out, or keep them together. Assign machines to a group and the platform honours it when placing them. Placement is decided when a machine starts, so a group affects new and restarted machines rather than rearranging running ones.

​
AutoScaling Groups

An autoscaling group manages a set of machines as one unit, adding and removing members according to the policy you define. You create a group through a wizard, and each group has a detail page for its members and activity.

​
VM Snapshots

A VM snapshot captures an entire machine at a point in time, as opposed to a volume snapshot, which captures a single disk.
VM Snapshots requires a per-account entitlement and is off by default. Without it the screen isn’t in your sidebar, and navigating to it directly returns you to Virtual Machines. Contact support if you need it enabled — the feature is functional but its interface is known to be rough, which is why it’s opt-in.

​
Kubernetes

Managed Kubernetes clusters, with a list and a per-cluster detail page.
Kubernetes is an internal preview, visible only to platform administrators. Its cluster detail tabs for workloads, configuration, monitoring, and security are placeholders that read “coming soon”. Don’t plan production work on it yet.

​
Deployments

Deployments sits above Compute in the sidebar and groups resources deployed together as a unit.
Deployments is an internal preview, visible only to platform administrators. Some of its error handling still surfaces raw browser alerts, and its resize control is unfinished.

Storage

Volumes to attach, snapshots, and backups.

Networking

The VPC your machines attach to, and how to publish them.

Images

Templates and ISOs — what a machine boots from.

Monitor

Whether your last action finished.