How It Works

Payment to a running machine, without a ticket.

Provisioning is automated from a prepared template. This page is the exact path an order takes, and what you get at the end of it.

The provisioning path

01

Choose a tier and cycle

The tier sets cores, memory and storage. The cycle sets how often the invoice recurs.

02

Checkout

Payment is taken by the payment processor. The order is created against live capacity, so a sold-out tier cannot be bought by mistake.

03

Automated build

A machine is cloned from the prepared template, its network identity is set, and it is powered on.

04

Delivery

Credentials and endpoints are issued through the client area and by email, including the API key where the plan includes one.

05

Access

RDP for normal use, the vSphere console when RDP is unavailable, and OpenWebUI where AgentOS is included.

Access and control

vSphere console

Out-of-band access from a browser, including a phone. Useful when a firewall change locks you out of RDP.

https://151.242.97.181:18443

API keys

Issued per account, visible in the client area. Rotate a key at any time if it leaks.

Per account

Support

Open a ticket from the client area. Infrastructure faults are handled directly; application issues are yours to own.

Client area

What is automated, and what is yours

We automate the machine: the template, the network identity, the power state and the handover. We do not automate your application, your database schema or your backups — those are yours to run and yours to keep.

If a machine fails at the host level, we repair or replace it. That is a different promise from backing up your data, and it is worth reading the terms before you rely on either.

Questions before you order?

The FAQ covers billing cycles, cycles that are not offered, cancellation and what happens on a failed renewal.

Read the FAQ