Back
CoreWeave vs Thunder Compute (August 2025)
A100 80 GB price snapshot and feature‑by‑feature comparison for ML teams
Published:
Aug 1, 2025
Last updated:
Aug 1, 2025

1. Pricing snapshot – A100 80 GB on‑demand
Provider | Hourly rate | Billing granularity | Annual savings vs CoreWeave |
---|---|---|---|
Thunder Compute | $0.78 / GPU‑hour | Per second | 70–75 % cheaper |
CoreWeave | $2.21–$2.70 / GPU‑hour | Hourly meter (rounded) | — |
Thunder Compute rate is their current published price for on-demand A100 80 GB. CoreWeave pricing is based on their public pricing table and aggregator listings for single-GPU SXM SKUs.
2. Billing & minimum commitment
Thunder Compute bills per second with no minimum; ideal for quick experiments or CI jobs.
CoreWeave advertises on-demand hourly pricing; usage is metered hourly, so short sessions pay for the full hour.
Takeaway: If you spin up notebooks for <60 minutes at a time, Thunder Compute’s fine-grained meter typically saves an extra 5–25 %.
3. Developer experience
Feature | Thunder Compute | CoreWeave |
---|---|---|
One‑click VS Code in browser | ✅ (built‑in) | ❌ |
Kubernetes knowledge required | No | Yes – platform is K8s native |
Live hardware swaps | Yes (any time) | Limited |
Snapshot & persistent root disk | Included | Requires separate storage class |
Thunder Compute focuses on bottoms-up engineers who want to “click → code.” CoreWeave targets ops teams comfortable managing clusters.
4. Storage & data management
Storage type | Thunder Compute | CoreWeave |
---|---|---|
Block / root volume | $0.15 / GB‑mo | $0.04–$0.07 / GB‑mo (block/NVMe) |
S3‑style object | N/A | $0.11 / GB‑mo (active tier) |
Thunder Compute’s persistent disk is automatically attached to every instance, making snapshots and restarts seamless. CoreWeave’s storage is cheaper, but may require more manual setup and management.
5. Lock‑in & contracts
Thunder Compute has no term commitments and supports standard SSH plus a convenient VS Code extension
CoreWeave offers marketplace reservations and capacity contracts (commonly 1–3 years for volume discounts) – useful for large clusters, but adds vendor lock-in.
6. When Thunder Compute wins
You need cheap A100s for interactive fine‑tuning or prototyping
Jobs are bursty or short-lived – per-second billing avoids wasted spend
Your team prefers VS Code over YAML manifests
You want to live-resize RAM, vCPUs, and storage without redeploying
7. When CoreWeave wins
You already run Kubernetes at scale and want full cluster control
You need InfiniBand multi-GPU nodes or H100 clusters today (Thunder’s H100 launch is slated soon at $1.47/hr)
Storage costs dominate and you have workflows built around cheap block and object storage tiers
Bottom line
At $0.78 per A100 80 GB, Thunder Compute undercuts CoreWeave by roughly 3× on raw GPU price and adds second-by-second billing plus VS Code convenience. CoreWeave still shines for teams that need large, reserved clusters and are happy living in Kubernetes. For most startups and indie ML engineers, Thunder Compute is the faster, cheaper on-ramp.

Carl Peterson
Other articles you might like
Learn more about how Thunder Compute will virtualize all GPUs
Try Thunder Compute
Start building AI/ML with the world's cheapest GPUs