RESOURCES
Paying by the hour for a need that is heavy some of the time. No rates are published yet.
Articles in Economics
- Economics
What a published rate would have to cover
No hourly rate has been published for the network, and none will be until access opens. This is what such a rate would have to account for, so a reader can judge it when it arrives.
· 4 min read
- Economics
Bursty demand and the shape of a team's year
Plot a team's compute demand across a year and it looks like a handful of spikes with quiet stretches between. That shape is why the network is being designed around jobs rather than machines.
· 4 min read
- Economics
When owning compute makes sense, and when renting does
Own compute when it is busy most of the time or when the work cannot wait. Rent it when it would sit idle most of the time and the work can wait for a queue. Most teams have some of each.
· 4 min read
- Economics
Idle capacity is the cost nobody budgets
Every compute budget has a line for the hardware and none for the hours it spends waiting. Idle capacity is paid in full and recorded nowhere, and the network is being designed to take it off the team's bill.
· 4 min read
- Economics
By the hour, not by the month
A monthly bill measures time that passed. An hourly bill for a job measures time that was used. The network is being designed so the meter starts when compute is held for a job and stops when it is released.
· 4 min read
- Economics
Paying for the peak at the trough
A team that owns compute sizes it for the busiest week and pays for it every other week. The network is being designed so the peak is paid for when it happens and the trough costs nothing.
· 4 min read