Starter
375 SAR/mo
- Credit issued
- 375 SAR
- Rate discount
- 15%
- Use case
- Solo builders and early internal tools
Pricing
Saudi GPU pricing without hidden starts.
DCP has two renter SKUs: pay-as-you-go balance and monthly credit commits. The API checks balance before dispatch. If credit is missing, it returns402 insufficient_balancebefore any provider starts work.
Balance flow
How money moves before a request reaches a GPU
The important parts are explicit: credit order, optional auto-top-up, and the insufficient-balance gate. This is what keeps billing predictable for renters and prevents unpaid provider work.
01
Starter credit first
New renter accounts start with 100 SAR credit. Usage draws from expiring credits before paid balance.
no card required
02
Auto-top-up when enabled
Saved-card renters can set a threshold, recharge amount, and monthly cap. A 3D Secure step-up is handled before credit is granted.
cap controlled by renter
03
402 before work starts
If balance cannot cover the pre-flight estimate, the API returns insufficient_balance instead of starting an unpaid job.
no silent negative balance
Model classes
Per-million-token rates by model class
Token rates are class-based so renters can estimate before picking a model. Subscription discounts multiply each class rate; premium models remain premium on every tier.
| Model class | Typical models | Best fit | PAYG | Starter | Growth | Scale |
|---|---|---|---|---|---|---|
| Embedding | bge-m3 | Retrieval, RAG indexing, search pipelines | 5h/M | 5 | 4 | 4 |
| Tiny | TinyLlama 1B, qwen2.5vl:3b, Gemma-2B | Cheap classification, extraction, vision previews | 15h/M | 13 | 12 | 11 |
| Small | qwen3:8b, Mistral-7B, Llama-3-8B, ALLaM-7B | Production chat, summaries, support agents | 30h/M | 26 | 24 | 21 |
| Medium | Qwen 3.6-27B-MTP, Qwen2.5-Coder-32B | Coding, long-context reasoning, bilingual workflows | 150h/M | 128 | 117 | 105 |
| Large | Future 70B class | High-end reasoning when the catalog has capacity | 400h/M | 340 | 312 | 280 |
h/M means halala per million tokens. Source: backend model-class rate table. The live API may return only models whose providers pass catalog and routing checks.
Monthly commits
Subscription credit is a discount ledger, not a different product
Each plan issues the same amount in platform credit every month. The discount applies to model-class token rates, then PAYG balance covers any overage.
Growth
default1,500 SAR/mo
- Credit issued
- 1,500 SAR
- Rate discount
- 22%
- Use case
- Production teams with recurring inference
Scale
5,625 SAR/mo
- Credit issued
- 5,625 SAR
- Rate discount
- 30%
- Use case
- Heavy workloads and private capacity planning
GPU time
Raw GPU-hour floor for jobs that bill by active runtime
Some control-plane jobs still settle against active GPU time. The values below mirror the backend GPU rate table at SAR/USD 3.75.
| GPU | Class | Min VRAM | SAR/hour | Halala/min | USD/hour |
|---|---|---|---|---|---|
| NVIDIA H200 | enterprise | 141 GB | 9.19 | 16 | 2.450 |
| NVIDIA H100 | enterprise | 80 GB | 7.09 | 12 | 1.890 |
| NVIDIA A100 | high | 40 GB | 4.50 | 8 | 1.200 |
| NVIDIA RTX 4090 | standard | 24 GB | 1.00 | 2 | 0.267 |
| NVIDIA RTX 4080 | standard | 16 GB | 0.67 | 2 | 0.178 |
| NVIDIA RTX 3090 | standard | 24 GB | 0.50 | 1 | 0.134 |
| NVIDIA RTX 3080 | entry | 10 GB | 0.33 | 1 | 0.089 |
Examples
Concrete balances, before a renter ships traffic
These examples are intentionally plain. They show how the same balance behaves across token classes, auto-top-up, and failed delivery.
333M
Approximate small-model tokens from starter credit
100 SAR starter credit at 30 halala per million tokens gives roughly 333 million small-class tokens before paid balance is needed.
Medium class
66M tokens
100 SAR at 150 halala/M, before subscription discounts.
Auto-top-up cap
renter set
Threshold, recharge amount, and monthly cap are configured from billing settings.
Failed delivery
credited back
Undelivered jobs are credited automatically; unused paid balance can enter refund review.
Corporate billing
available
Monthly invoicing is available through billing@dcp.sa; tax-invoice details are confirmed per account.
Policy
Refunds and data residency
Refund requests for paid top-ups are submitted from the renter payment record and reviewed by an admin. Approved card refunds are sent through Moyasar when the original payment has a Moyasar id; bank-transfer or sandbox records use the internal/manual refund path.
DCP recruits providers for Saudi-hosted compute and does not use prompts or completions for model training. Some platform infrastructure (web frontend, billing metadata) currently runs outside the Kingdom; see the Privacy Policy for the current data-location disclosure. Billing records are retained for reconciliation and audit.