Billing
redu.cloud uses metered hourly billing. You are charged for what you use, measured every hour. Credits are applied before any Stripe charge.
How billing works
Every hour, the platform records usage for all active resources:
| Resource | Billed on |
|---|---|
| Instances | Per hour, per flavor |
| Volumes | Per GB per hour |
| Snapshots | Per GB per hour |
| Private networks | Per hour |
| Volume backups | Per GB per hour |
| Egress | Per GB above the free tier |
Hourly records are batched and pushed to Stripe as meter events — your invoice reflects actual consumption, not a flat subscription.
Free egress tier
The first 2 TB of outbound traffic per month is free. Usage above that is billed at the standard egress rate shown in your pricing rules.
Credits
Credits are applied before any Stripe charge. If you have a credit balance, it is consumed first each billing cycle.
amount_charged = max(0, usage_cost - credit_balance)Credits have an expiry date. Expired credits are not applied. You can view your remaining credits and their expiry dates on the Billing page.
Credits are granted by the redu.cloud team (promotional, compensation, or referral). Admin users can grant credits via the Admin panel.
Cost forecast
The Billing page shows a real-time forecast based on your current active resources and their hourly rates. This is an estimate — actual invoices may differ slightly.
The forecast is also shown on the Overview page for quick reference without navigating away.
Billing states
| State | Meaning |
|---|---|
active | Billing is healthy, charges processing normally |
trial | Trial period, charges may be reduced or waived |
past_due | A payment failed — resource creation is blocked |
for_deletion | Account has been past due for more than 3 days — instances will be stopped |
canceled | Subscription cancelled |
When an account reaches past_due or for_deletion, new instances, volumes, clusters, and load balancers cannot be created until billing is resolved.
What happens on payment failure
- Stripe webhook fires
invoice.payment_failed - Account status moves to
past_due - Resource creation is blocked
- After 3 days of non-payment, status moves to
for_deletion— running instances are stopped and proxy hosts are disabled - Once payment succeeds, status resets to
activeautomatically
Pricing
Hourly rates are configured per resource type and flavor in the pricing_rules table. Contact support@redu.cloud for current pricing.