Introduction
KVM cloud servers on NVMe, managed from the dashboard or the API.
Each server is a full KVM virtual machine with its own kernel, local NVMe storage and a dedicated IPv4 address. You manage servers from the dashboard or the REST API, on your own or with a team.
What you get#
- Servers running Ubuntu, Debian, AlmaLinux, Rocky Linux or Windows Server, with power controls, rebuilds and reverse DNS. See Servers.
- Snapshots to try a risky change and then keep it or roll it back. See Snapshots.
- Backups taken daily at an hour you choose, kept for as many days as you set. See Backups.
- SSH keys saved once and added to new and rebuilt servers. See SSH keys.
- Workspaces for teams, with roles for who can do what. See Workspaces and members.
- API tokens scoped to the actions a script needs. See API tokens.
How it fits together#
Everything lives in a workspace. You get a personal one when you sign up, and you can create team workspaces and invite people to them. A workspace has its own servers, SSH keys, backups, billing and API tokens.
Actions on a server, such as starting or rebuilding it, are queued operations. The request returns straight away with an operation, and the server’s activity shows it go from queued to running to done.
Where to next#
- New here? Start with the Quickstart.
- Automating? Create an API token, then browse the API reference.