# On-Demand vs Spot

Clore.ai offers two rental types with different trade-offs. This guide helps you choose the right one.

## Quick Comparison

| Feature                         | On-Demand           | Spot               |
| ------------------------------- | ------------------- | ------------------ |
| **Guaranteed access**           | ✅ Yes               | ❌ No               |
| **Can be interrupted**          | ❌ No                | ✅ Yes (outbid)     |
| **Base fee**                    | 10%                 | 2.5%               |
| **Fee with max PoH (2M CLORE)** | 5%                  | 1.25%              |
| **Best for**                    | Training, rendering | Mining, batch jobs |

## On-Demand Rental

### How It Works

* You pay a fixed price for guaranteed GPU access
* No one can take over your rental
* Runs for your specified duration (6h - 3000h)

### Best Use Cases

* **ML/AI training** - Long training runs that can't be interrupted
* **3D rendering** - Projects with deadlines
* **Development** - When you need reliable access
* **Production workloads** - Critical tasks

### Pros

* Guaranteed uptime
* Predictable costs
* No risk of interruption

### Cons

* Higher fees (10% vs 2.5%)
* Less flexible pricing

***

## Spot Rental

### How It Works

* You bid a price for GPU access
* Other users can outbid you at any time
* If outbid, your rental ends and you stop paying

### Best Use Cases

* **Cryptocurrency mining** - Can handle interruptions
* **Batch processing** - Jobs that can be restarted
* **Testing** - Quick experiments
* **Fault-tolerant workloads** - With checkpoint/resume

### Pros

* Much lower fees (2.5% vs 10%)
* Cost-effective for flexible workloads
* Good for price-sensitive users

### Cons

* Can be interrupted anytime
* Not suitable for critical tasks
* Need to handle interruptions in your workflow

***

## When to Use Each

### Choose On-Demand when:

* ✅ Your task cannot be interrupted
* ✅ You have a deadline
* ✅ Training a model that doesn't checkpoint well
* ✅ Running production services
* ✅ You need guaranteed availability

### Choose Spot when:

* ✅ Your workload can handle interruptions
* ✅ You're mining cryptocurrency
* ✅ Running batch jobs with checkpointing
* ✅ Cost is your primary concern
* ✅ You're doing quick tests or experiments

***

## Cost Example

Renting a GPU at 10 CLORE/day for 7 days:

| Type      | Base Cost | Fee               | Total           |
| --------- | --------- | ----------------- | --------------- |
| On-Demand | 70 CLORE  | 7 CLORE (10%)     | **77 CLORE**    |
| Spot      | 70 CLORE  | 1.75 CLORE (2.5%) | **71.75 CLORE** |

**Savings with Spot:** 5.25 CLORE (6.8%)

With max PoH (2M+ CLORE in PoH):

| Type      | Base Cost | Fee                 | Total            |
| --------- | --------- | ------------------- | ---------------- |
| On-Demand | 70 CLORE  | 3.5 CLORE (5%)      | **73.5 CLORE**   |
| Spot      | 70 CLORE  | 0.875 CLORE (1.25%) | **70.875 CLORE** |

> **Note on Bitcoin payments:** When paying with BTC, hosts may face an additional 15% extra hoster fee, which can be reduced to 0% through [MFP Lock](/for-hosts/mfp-lock-a-complete-breakdown-of-mechanics.md). CLORE payments have no extra fees. See [Fee Structure](/for-renters/fee-structure.md) for details.

***

## Tips

1. **Start with Spot** for testing, switch to On-Demand for production
2. **Use checkpointing** if using Spot for training
3. **Monitor your Spot rentals** - set up alerts for when you're outbid
4. **Hold CLORE in PoH** to reduce fees on both types (up to 50% at 2M CLORE)
5. **Pay with CLORE** when possible to avoid extra currency fees on hosts


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.clore.ai/for-renters/on-demand-vs-spot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.