'%20d='M364.9%20143.2v98.9l-1.4%201.2-165.6%20140.4%2035.7%2029.7v-34.2l1.4-1.2%20123.4-105.4%206.5-5.6v37l-1.3%201.2-99.7%2085.8v84.7l-6.6-5.7-97-83.1-3.6-3%203.5-3%20174.4-150.6v-25.1L153.7%20360.5l-6.6%205.7v-98.9l1.4-1.2%20161.6-138-35.7-29.7v34.4L273%20134%20153.7%20236.7l-6.6%205.7v-37l1.3-1.2%2097-83.2V36.3L252%2042l97.1%2083.1%203.6%203-3.6%203-171.7%20147.7V304l106.2-90.6%2056.4-48.8%2018.3-15.7z'%20/%3e%3c/svg%3e)
The cloud, withoutthe cloud account
You want a machine for an afternoon.The cloud wants an account, keys and a quota request.We hold all of that, so you can buy an hour instead.
What one machine normally costs you
Before the machine runs, and before anything is computed.
An account and a card
Signed up, verified and attached to a payment method before a single machine exists.
Keys and permissions
Access keys to create, and the policies that decide what those keys are allowed to do.
A quota request
GPU capacity is limited by default, and the answer arrives when it arrives.
The resources underneath
One machine on Azure needs six: a network, a subnet, an address, a firewall, a card, a disk.
What you do instead
Four steps, and the longest one is the cloud handing the machine over.
Sign in
Google, GitHub or LinkedIn. No cloud account of your own, and no keys to hold.
Buy credit
A balance you top up. Every machine spends from it, and nothing is billed afterwards.
Pick a machine
Cores, memory, GPU and disk, with the price per hour beside each one.
Work, then stop it
Open a shell, run the work, and stop the machine when it is finished.
How the bill works
Everything is paid first, and counted from periods we wrote down.
Credit comes first
You top up a balance, and machines spend from it. No invoice arrives later.
Hours round up
Five minutes costs an hour. A restart inside a paid hour costs nothing.
The disk counts apart
It charges from the first run until deletion, even while the machine is off.
A day of headroom
Before a start, the balance must cover a day of everything you would run.
When the credit runs out
Four steps, in this order, so nothing disappears without an email first.
We warn you
An email while there are still hours left, saying when machines would stop and be deleted.
Machines stop
At zero, everything running is stopped. The disks stay, so nothing is lost yet.
We warn again
After a while at zero, a second email gives the date the machines would be deleted.
Then they go
If the wait passes with the balance still at zero, the machines and their disks are deleted.
Getting into a machine
The platform never connects to your machine on its own. These are the ways in.
A shell in the browser
A terminal on the machine from its panel, with no SSH client and no key on your laptop.
Your own key
Place a public key on a machine and reach it with the SSH client you already use.
Ports you open
Nothing is reachable until you open a port, and you can close it again from the panel.
Why you might not want us
We hold the cloud accounts, so you cannot bring your own or use a region we do not run in. Two people cannot share one server. We do not build object storage, monitoring or proxies, and we have no workflow engine of our own — where a machine wants one, that is dxflow's job.
If any of that is the thing you need, a cloud account of your own is the better answer, and we would rather say so here.