Cloud bill examples
Calculate complete small-service, backup, GPU, and hybrid bills with explicit assumptions.
A complete Infra estimate includes subscription, running allocations, retained data, and applicable transfer. Use Organization → Usage → Estimate or a resource creation review to apply the selected region's rate card.
Examples use 730 hours, monthly subscription billing, Standard support, and USD before tax. Storage values are the billable capacities defined by the service price reference.
Two-instance web service
The organization has five seats, two private s-2-4 droplets, 30 GiB of replicated
root storage per droplet, a redundant load balancer, and 30 GiB of managed backups.
Internet outbound is 200 GiB, within the pooled allowance.
The monthly estimate includes these subscription and resource charges:
| Item | Calculation | Monthly estimate |
|---|---|---|
| Subscription | $99 + 5 × $29 | $244.00 |
| Shared compute | 2 × $10 | $20.00 |
| Persistent root volumes | 60 GiB × $0.040 | $2.40 |
| Redundant load balancer | One service | $6.00 |
| Managed backup data | 30 GiB × $0.006 | $0.18 |
| Internet outbound | 200 GiB within allowance | $0.00 |
| Total | $272.58 |
The balancer's included IPv4 is not charged again. The droplets have no public addresses in this example. The compute table's optional scratch allowance is not counted as persistent root storage.
A ten-hour GPU job
An existing organization runs one L4 droplet for ten hours with 100 GiB of replicated
storage for those same hours, then removes both. Compute is 10 × $0.35 = $3.50.
Storage is 100 × $0.040 × 10 / 730, approximately $0.0548 before line rounding.
The added resource estimate is $3.55, excluding transfer outside the remaining
allowance and the organization's existing subscription.
Keeping the disk for the full month changes storage to $4.00 even if the job
ran for only ten hours. An idle retained IPv4 can add its prorated reservation
charge; removing a guest does not release independent resources automatically.
A 500 GiB regional recovery target
A replicated target volume is 500 × $0.040 = $20.00 for 730 hours. An initial
100 GiB private copy plus 50 GiB of later changed-data transfer is
150 × $0.003 = $0.45. The incremental estimate is $20.45, before any retained
snapshot-exclusive blocks or recovery-test compute.
The source volume remains a separate allocation. Transfer uses actual copied bytes, while target capacity uses its provisioned size. An empty portion of the logical target does not eliminate its capacity charge.
Existing self-hosted hardware with a hosted worker
An organization with five seats pays $244/month for the subscription while
managing its owned nodes. Creating one hosted d-2-8 worker for 730 hours adds
$20.00; retaining a 40 GiB replicated root disk adds $1.60. The total is
$265.60 before other cloud usage or external provider costs.
There is no extra Connector fee and no second hosted-compute bill for local guests. Internal allocation rates for owned hardware are an accounting model, not another Solarius resource charge.
Apply discounts and compare periods
A 12-month eligible dedicated-compute commitment reduces the worker's $20.00
compute line to $16.00; it does not discount its disk. Annual subscription
billing changes the base-plus-seat total to $2,440/year, paid separately from
ongoing metered resources.
Use reserved capacity to distinguish commercial commitments from idle physical holds, and spend caps for admission rather than treating an estimate as an enforced maximum invoice.