Shadeform vs Aquanode

Multi-cloud GPU marketplace with a single API across many clouds

Shadeform solves the same first half of the problem we do — one API across many GPU clouds instead of an account per vendor. Where we diverge is the second half: finding capacity is not the same as being able to take your environment with you when you move to it.

Where Shadeform wins

Broad first-party cloud coverage with a single API, and a clean deployment story for teams that mainly need capacity aggregation.
Reserved and long-term capacity brokerage across clouds, which we do not do.

Where Aquanode wins

Your environment survives the box. Pause a deployment, come back tomorrow, resume with packages, model weights and config intact — instead of rebuilding from a fresh image every session.
A snapshot taken on one provider restores onto another. Supply moved, price moved, or a region ran dry — the environment follows, rather than being stranded in the account that created it.
One account across every provider we broker, so you are not maintaining separate logins, keys and billing per vendor to chase capacity.
Automated backups are on by default when you attach storage at deploy time, at a 6-hour interval — you do not have to remember to configure them.

Shadeform pricing

We could not verify a Shadeform price first-party, so this page publishes none. Shadeform's pricing page returned HTTP 403 to our fetches on 2026-08-05, so we could not read a rate from their own site. We would rather publish nothing than quote a number sourced from somewhere else. Check their pricing page directly.

Checked https://www.shadeform.ai/pricing on 2026-08-05.

What we do not claim

Restoring an environment requires a snapshot that already exists. Stopping a deployment yourself captures it on the way out, so you can bring it back later on any provider. A provider-side termination is different: it is only recoverable if you had already switched automated snapshots on for that deployment, and it costs you the work since the last one. Automated snapshots are opt-in — nothing runs until you start it — and with none running there is nothing to restore.

`aq deploy --snapshot <id>` rents the cheapest matching GPU and restores your snapshot onto it — including onto a different provider than the one it came from. Creating the snapshot is a separate step today: the standalone ogre CLI on the box writes it.