API status.

What exists now

• Ordering through the configurator, with shareable configuration links.
• Sign-in with an account access key.
• Your server is a normal Linux or BSD VPS: use SSH, Ansible, Terraform with the provider you prefer inside it, or any tool you already use.

What is planned

Read-only order status and an authenticated reboot, reinstall and console endpoint are the first candidates. If you need API access for a project, tell us what you would automate. No dates are promised.

Automating a server today

You can already automate everything inside your server. Use SSH with key-based login, then manage it with Ansible, shell scripts, cloud-init-style provisioning or configuration tools you prefer. For rebuilds, keep your configuration in version control so a RAM-only instance can be restored in minutes.

Why there is no public API yet

Ordering and account access work through the configurator and your access key. A public API needs authentication that does not weaken the no-ID model, careful rate limits and a stable contract, so it is not offered until those are right.

Until then, anything inside your server is yours to automate with any tool you like: shell scripts, Ansible, Docker Compose or cron. See the Docker guide and the hardening checklist.

Common questions