AI Model Pricing
Use the table below as the technical reference layer for how different model families map to credit consumption.
These model-family rates are useful when technical teams want to reason more precisely about cost shape across lightweight generation, balanced day-to-day execution, and premium reasoning workflows.
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
A team can have low AI usage but meaningful infrastructure spend, or high AI usage with relatively low cloud runtime. These are independent levers and should be reviewed separately.
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 servicesExample 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.