Home How it Works Pricing CAP Model EU Hosting FAQ Upload

GPU Render Pricing Explained

GPU Render Studio uses a deterministic pricing model for Blender GPU rendering: fixed execution slots, optional overflow runtime, and configurable CAP limits for predictable total cost.

How Pricing Works

  1. Select a fixed execution slot.
  2. Optionally allow overflow runtime.
  3. Set a CAP limit for extra spending.
  4. Track runtime, billing and ETA in real time.

Slot Packages

Slot Base Runtime Price
StrictUp to 1.5 hours$0.50
ExtendedUp to 4 hours$2.00
FlexibleUp to 8 hours$4.00
OpenUp to 12 hours$5.00

The base slot price is always billed first and guarantees execution for the selected runtime window.

Overflow Billing

  • No overflow unless explicitly enabled.
  • Billed only after slot runtime is consumed.
  • Visible live in the status UI.

CAP Spending Limits

CAP defines how much extra you allow to spend after the base slot price. It never replaces the slot and only applies to overflow runtime.

Example:
Flexible Slot: 8h / $4.00
CAP Extra: $4.50
→ Maximum total: $8.50
→ Runtime ≈ 12.5h

  • CAP applies only to overflow.
  • CAP never triggers inside the slot window.
  • Jobs pause safely when CAP is reached.

Paused Jobs & Resume

When CAP is reached, the job transitions to paused_cap. Rendered frames are preserved and billing is locked.

Resume orchestration is planned for Phase 1.4.

What You Pay For

Real GPU Time

All billing reflects physical NVIDIA GPUs executing Blender scenes.

Successful Frames

Technical failures are never billed.

Audit Trail

Every job includes logs, timing data and billing breakdown.