AI Model Pricing
Use the table below as the technical reference layer for how different model families map to credit consumption.| Model | Family | Base input | Output | Cache write | Cache read |
|---|---|---|---|---|---|
| Claude 4.5 | Haiku | 1 credit | 5 credits | 1.25 credits | 0.10 credit |
| Claude 4.6 | Sonnet | 3 credits | 15 credits | 3.75 credits | 0.30 credit |
| Claude 4.5 | Sonnet | 3 credits | 15 credits | 3.75 credits | 0.30 credit |
| Claude 4.7 | Opus | 5 credits | 25 credits | 6.25 credits | 0.50 credit |
| Claude 4.6 | Opus | 5 credits | 25 credits | 6.25 credits | 0.50 credit |
| Claude 4.5 | Opus | 5 credits | 25 credits | 6.25 credits | 0.50 credit |
Infrastructure Billing
AI is not the same as hosting. Revolte also exposes managed infrastructure and delivery operations, and these can contribute separately to total cost. Public cloud pricing shown on pricing material is an estimate using the highest-cost region, and actual cloud costs vary by configured deployment region.Web App
Frontend hosting with global edge delivery, including custom domain management and automatic SSL/TLS.- Data transfer billed
- Core hosting shown as free of cost
Web Service
Serverless deployment for APIs, microservices, and compute workloads.- ALB: $0.042 / hr
- Storage: $0.08 / GB-month
- Registry: $0.10 / GB-month
Database
Managed data services with scalable storage and backup pricing.- Storage: $0.115 / GB-month
- Backup: $0.095 / GB-month
Secrets and Storage
Secrets, object storage, cache, metrics, network, and supporting platform primitives.- Secrets: $0.40 / secret-month
- Object storage: $0.023 / GB-month
| Category | Metric | Approx cost | What it means |
|---|---|---|---|
| Logs | Ingestion | $0.50 / GB | New logs written into the platform |
| Logs | Storage | $0.03 / GB-month | Retaining log data over time |
| Logs | Insights queries | $0.005 / GB scanned | Interactive analysis over retained logs |
| Pipeline | Linux medium build minutes | $0.01 / min | Build and pipeline execution time |
| Metrics | Custom metrics | $0.30 / metric-month | Custom observability signals retained monthly |
| Metrics | Alarms | $0.10 / alarm-month | Configured operational alert objects |
| Object storage | Standard storage | $0.023 / GB-month | Stored files and assets |
| Object storage | GET requests | $0.0004 / 1K requests | Read access to stored objects |
| Object storage | PUT / COPY / POST / LIST | $0.005 / 1K requests | Write and listing activity |
| Network | Internet egress | $0.09 / GB first 10TB | Outbound traffic served to users or systems |
| Network | DNS | $0.50 / hosted zone-month | Managed DNS zone cost |
| Secret store | Storage | $0.40 / secret-month | Stored secrets under management |
| Secret store | API calls | $0.05 / 10K requests | Programmatic secret retrieval or management calls |
| Cache | Storage | $0.085 / GB-month | In-memory cache capacity |
Cost Estimation
The safest way to estimate Revolte cost is to break it into layers rather than chase one all-in number. Start with the plan, then calculate likely overages, then add infrastructure only for the services you actually run.Step 1 — Pick the right plan
Choose based on service count, environments, CI/CD run volume, and whether you need BYOC or enterprise controls.Step 2 — Estimate delivery overages
Measure likely token usage, CI/CD runs above plan limits, and log growth above the included monthly quota.Step 3 — Add runtime infrastructure
Include only the services you deploy: web services, databases, object storage, cache, secrets, metrics, and network egress. Total monthly estimate ≈ base plan + AI overage + CI/CD overage + log overage + cloud runtime services| Team pattern | Best starting plan | Primary cost drivers | What to watch first |
|---|---|---|---|
| Solo builder validating the platform | Free | AI prompts, a few CI runs, light logs | Whether experimentation stays inside 5 credits, 500 runs, and 5 GB logs |
| Small startup with a few active services | Pro | CI/CD volume, preview environments, web services, logs | Run frequency, preview sprawl, and whether AI-heavy workflows are repeated too broadly |
| Growing multi-service team | Pro or Enterprise | Service count, logs, object storage, database growth, support expectations | When service count, compliance, or control needs exceed standard Pro boundaries |
| Regulated or platform-scale organization | Enterprise | Custom caps, SLA, BYOC, compliance modules, large runtime footprint | Private cloud, on-prem, audit support, SSO/RBAC, and modular product packaging |
Example overage math
If a team exceeds its included log quota by 20 GB in a month, the listed PAYG log ingestion rate implies:20 GB × $0.50 = $10.00
This is separate from any retained log storage or log query scanning cost.
Another simple calculation
If a team exceeds its CI allowance by 1,000 runs, the listed PAYG CI run rate implies:1,000 runs × $0.01 = $10.00
This should be monitored alongside build-minute-based pipeline cost and infrastructure usage.