These terms govern your use of SpotGPUs — the website at spotgpus.com, the console at cloud.spotgpus.com, and the compute, storage and network services they give access to. By creating an account or using the service, you accept them.
1. Who this is between#
1.1 “We”, “us” and “SpotGPUs” mean the operator of the service. “You” means the person or the organisation holding the account. If you accept these terms on behalf of an organisation, you confirm that you may bind it.
1.2 Operator identification — legal name, registered seat and registration number — is provided on request through the contact form before you enter into a contract, and is stated in the order form for business accounts and reserved capacity.
1.3 These terms, the acceptable use policy, the service level agreement, the privacy policy and, where it applies, the data processing addendum form the whole agreement. Where a signed order form conflicts with them, the order form wins for the services it covers.
2. Your account#
2.1 You must be at least 18 and able to enter into a contract. One person or organisation, one account; do not share credentials.
2.2 You are responsible for what happens under your account, including anything done with your API keys or SSH keys. Enable two-factor authentication if the account holds credit — we provide it, you decide.
2.3 Tell us without delay if you believe an account, a key or a session has been compromised. We can revoke sessions and keys immediately; we cannot undo spending that has already happened.
2.4 The email address on the account is how we reach you about billing, security and service changes. Keep it working.
3. The service#
3.1 We provide virtual machines with dedicated GPUs, persistent network volumes, and the network needed to reach them, in the regions listed on the site.
3.2 Instances are created from a template or from an image you supply. What runs inside the instance is yours to choose, install, configure, secure and back up.
3.3 Capacity is finite. We do not guarantee that a given GPU model is available in a given region at a given moment, except where you hold reserved capacity, which is allocated to you for its term.
3.4 We may change the catalogue: adding models, retiring hardware, or changing node sizes. Retirement of a model you are actively using is announced with at least 30 days' notice, except where a safety or a supplier failure makes that impossible.
4. Tiers and interruptions#
4.1 Spot instances run on capacity we may reclaim. Before a planned reclaim we publish a notice at least 2 minutes ahead on the instance metadata endpoint, through the configured webhook and in the console. At the end of that window the instance is stopped.
4.2 A reclaim stops the instance; it does not delete it. Persistent volumes, their contents and the reserved address remain. Compute is not billed after the stop.
4.3 No availability target applies to spot instances, and reclaim rates published on the site are measurements of the past, not promises about the future.
4.4 On-demand instances are not reclaimed for capacity reasons and are covered by the SLA. We may still stop an instance for non-payment, for a breach of the acceptable use policy, or in an emergency affecting the physical node.
4.5 Reserved capacity is confirmed in writing for a term, at a fixed rate, and is not reclaimed during that term.
5. Prices and payment#
5.1 The service is prepaid. You add credit to the account balance and it is drawn down as you use the service. The minimum top-up is $40; credit does not expire.
5.2 Compute is billed per started minute, at the published hourly price of the instance divided by 60, from the moment the instance becomes reachable until it stops. Persistent storage is billed at $0.08 per GB-month, prorated, from the creation of a volume until you delete it — including while the attached instance is stopped.
5.3 The price that applies to a running instance is the one shown when it was launched. Published prices may change for future instances; we do not reprice work that is already running.
5.4 Deployment requires a balance covering at least one hour of the instance rate. If the balance reaches zero, running instances are stopped. Volumes survive and continue to be billed until deleted.
5.5 Taxes, where they apply, are added to the amounts payable. You are responsible for any tax on your own use of the service.
5.6 Refunds. Consumed compute and storage are not refundable. Unused credit can be refunded on request, less any transaction cost, for as long as the account is in good standing; refunds are returned by the route the payment arrived. Credit obtained through a promotion is not refundable.
5.7 Billing errors happen. Tell us within 60 days and we will investigate and correct genuine errors, in both directions.
6. Your content#
6.1 Everything you upload, install, generate or store stays yours. We claim no rights over it, and we do not use it to train anything.
6.2 We access customer instances and volumes only to operate the platform — for example to investigate a hardware fault — and when you ask us to look at something. Volumes are encrypted at rest.
6.3 You are responsible for backups. A volume is storage, not a backup: copy anything irreplaceable out of the platform. There are no egress fees to stop you.
6.4 You must have the rights you need for what you run: data, models, weights, container images and licences.
7. Acceptable use#
7.1 The acceptable use policy is part of these terms. In short: nothing illegal, nothing that attacks other systems, nothing that abuses the shared network, and no misrepresentation of who is behind a workload.
7.2 Reports of abuse are handled through the abuse form. We act on the evidence, not on volume of complaints.
8. Suspension and closure#
8.1 We may suspend an instance or an account without prior notice where there is active abuse, a security emergency, a legal obligation, or a payment failure. Where notice is possible, we give it.
8.2 You can close your account at any time from the console. Closing stops instances and ends billing; delete your volumes first if you do not want them retained and billed.
8.3 After closure, we keep the records we must keep — billing and payment history — for the periods set in the privacy policy, and delete the rest.
8.4 If we terminate the agreement for a reason that is not your breach, we refund unused credit.
9. Availability#
9.1 On-demand and reserved instances are covered by the SLA, with a monthly availability target of 99.9% and service credits below it. Those credits are the sole remedy for unavailability.
9.2 Planned maintenance that can affect running instances is announced in advance by email and on the status page. Emergency maintenance may happen without notice.
9.3 The service is provided as it is. Beyond what the SLA promises and what the law requires, we make no warranty that it will be uninterrupted, error-free, or fit for a particular purpose.
10. Liability#
10.1 Neither side is liable for indirect or consequential loss: lost profit, lost revenue, lost data beyond the cost of restoring it, lost opportunity, or the cost of substitute services.
10.2 Our total liability arising from the agreement, in any twelve-month period, is limited to the amounts you paid us in the three months before the event that caused the claim.
10.3 Nothing here excludes liability for fraud, for wilful misconduct, for death or personal injury caused by negligence, or for anything else that cannot be excluded by law.
10.4 Because spot capacity is interruptible by design, an interruption of a spot instance after a valid notice is never a breach of this agreement.
11. Indemnity#
You will cover us against third-party claims arising from what you ran on the service — the content, the data, the models, the traffic — where the claim would not have existed but for your use, and where it is not caused by our own breach. We will tell you promptly about any such claim and let you conduct the defence.
12. Changes#
12.1 We may change these terms. Material changes are announced to account holders by email at least 30 days before they take effect, and the revision date at the top of this page always reflects the current version.
12.2 If a material change does not suit you, stop using the service before it takes effect and ask for a refund of unused credit. Continuing to use the service after that date is acceptance.
13. Data protection#
How we handle personal data is described in the privacy policy. Where you use the service to process personal data for which you are the controller, the data processing addendum applies and forms part of this agreement.
14. Export control and sanctions#
You confirm that you are not subject to sanctions that would prohibit us from supplying you, that you will not make the service available to a sanctioned party, and that you will not use it in breach of export control rules that apply to you — including any that apply to the hardware itself.
15. Law and disputes#
15.1 Talk to us first. Most disputes are a misunderstanding about a charge or an interruption, and a message resolves them faster than anything else.
15.2 The governing law and the competent court are those of the operator's registered seat, identified on request under clause 1.2 and stated in the order form for business accounts. Mandatory consumer protections in your country of residence are not affected.
15.3 If a clause is held unenforceable, the rest stays in force.
15.4 You may not transfer the agreement without our consent. We may transfer it to a successor of the business, and will tell you if that happens.
16. Contact#
Contractual questions, notices under these terms and refund requests: the contact form, or a ticket in the console if you have an account. Abuse and security reports: the abuse form.