RunPod vs Aquanode
GPU cloud with community and secure pods plus serverless endpoints
RunPod is a strong default for spinning a GPU up quickly and has a much larger template and community ecosystem than we do. The difference shows up on the second session: a RunPod pod's environment lives inside RunPod, while an Aquanode environment is saved off the box and can be restored onto a different provider entirely.
Where RunPod wins
- A far bigger template library and community catalogue: for most popular stacks there is already a working RunPod template.
- Serverless endpoints that cold-start in seconds. Our jobs scale to zero too, but ours wake a whole box at a provider, so the first request after an idle period waits minutes rather than seconds. For bursty request/response traffic that has to answer immediately, RunPod is the right shape. We are built for work that runs for minutes or hours, where a multi-minute start is amortised and what matters is whether the job finishes.
- Community Cloud pricing undercuts most secure capacity, ours included, when you are willing to take the availability trade.
Where Aquanode wins
- Your setup outlives the GPU you rented it on. Save the environment (custom nodes, model weights, packages, the config you spent an evening getting right) and bring it back up later on a completely different provider, instead of reinstalling it from scratch every session.
- Supply moved, the price moved, or the region ran dry. Your environment follows you out. It is not stranded in the account that happened to create it, which is the part that makes leaving any single vendor cheap.
- Pause and resume in place on every provider we support: it's a snapshot-and-terminate, then a fresh box restored from that snapshot, the same mechanism everywhere. (Voltage Park's adapter supports it too, it just has no live GPUs to rent right now.) On any provider, the same environment also comes back by restoring your saved setup onto a fresh box, a little slower, same result.
- Turn on automatic snapshots yourself and pick the interval (as often as every 15 minutes, 30 by default) instead of remembering to snapshot by hand or wiring up your own cron job.
- One account, one bill and one set of keys across every provider we support, rather than a separate login and invoice per vendor every time you chase capacity.
- Run a saved version of your setup as a job. If a provider takes the box back mid-run, we detect the loss and queue the run to retry on a different provider, excluding the one that just lost it, and if the job checkpoints the next attempt picks up from the last one. Jobs scale to zero when the queue empties, so an idle one is not sitting on a rented GPU, and every job is bounded in the unit we bill: its time limit times its attempts times its machines is the most a single run can cost.
RunPod pricing vs Aquanode
RunPod figures are Secure Cloud on-demand, per GPU, read from their own pricing page on 2026-08-05. The Aquanode column is the lowest live per-GPU rate in our marketplace feed and moves on its own. The two columns are not measured the same way, so treat this as a starting point, not a quote.
Source: https://www.runpod.io/pricing, Secure Cloud on-demand, per GPU. Verified 2026-08-05. Vendors change prices; check theirs before deciding.
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.
RunPod vs Aquanode: common questions
Can I move a RunPod environment to Aquanode?
Not automatically. There is no RunPod import. What you can do is snapshot an Aquanode environment once you have built it here and restore that snapshot onto any provider we support, which is the part that does not exist inside RunPod.
Is Aquanode cheaper than RunPod?
Sometimes, and it depends entirely on the day and the model. We search across many providers, so the cheapest listing moves. Compare the live rates on this page against RunPod's published Secure Cloud rates rather than trusting a blanket claim. Cheap per hour is a commodity; the environment surviving between sessions is the thing that is hard to replace.
Does RunPod persist my environment between sessions?
RunPod offers network volumes that persist data, and they work well. The limit is scope: that volume lives in RunPod. An Aquanode snapshot can be restored onto a different provider, which is what matters when capacity or price moves.
Is RunPod free?
No. RunPod publishes an hourly rate for every GPU it rents, and charges for storage on top: $0.10/GB/mo for container disk and for a volume disk while it is running, $0.20/GB/mo for a volume disk while it is idle, and network storage from $0.05 to $0.14/GB/mo depending on tier and size.
Source: https://www.runpod.io/pricing, read 2026-09-02.
What is the difference between RunPod Secure Cloud and Community Cloud?
RunPod's own documentation describes Secure Cloud as operating in T3/T4 data centers, providing high reliability and security for enterprise and production workloads, and Community Cloud as connecting individual compute providers to users through a vetted, secure peer-to-peer system with competitive pricing. Both bill pods by the minute with no fees for ingress or egress.
Source: https://docs.runpod.io/pods/overview, read 2026-09-02.
