Billing and Costs
How CPU, memory and storage consumption becomes a transparent monthly invoice.
gh0stcloud billing is designed for full auditability. Every cost driver is visible in real time and the monthly invoice can be broken down to namespace level in the portal.
Principle: No hidden overhead charges. What you're billed for is exactly what was measured for your namespace — plus the contractually defined platform fee.
Cost model — the formula
The platform calculates costs from three weighted consumption dimensions:
| Dimension | Measurement |
|---|---|
| CPU | Consumption per namespace, aggregated hourly |
| Memory | Consumption per namespace, aggregated hourly |
| Storage | Persistent volume usage, aggregated hourly |
The exact weighting reflects the actual cost structure of our infrastructure. Under Enterprise contracts, weighting can be negotiated.
Billing cadence
The platform runs three aggregation stages:
| Step | Interval | Output |
|---|---|---|
| Hourly metering | Hourly | Raw consumption data per namespace is read and persisted |
| Daily normalization | Daily | Hours are normalized to daily values, outliers smoothed |
| Monthly close | Monthly | Invoice summary is created and sent as a PDF via Lexoffice |
What an invoice contains
| Line item | Description |
|---|---|
| Runtime usage | Weighted consumption of compute, memory and storage for the billing period |
| Platform fee | Fixed monthly fee per the contracted tier |
| Net amount | Sum of the above |
| VAT 19% | Applied per German tax law |
| Total | Final invoice amount |
Invoices are generated automatically via gh0stplane and delivered as PDF by email. Optionally booked services (dedicated bare-metal, managed add-ons, extended SLA tiers) appear as separate line items.
FinOps dashboard in the portal
The gh0stportal FinOps dashboard shows:
- Real-time usage — CPU, memory, storage per namespace, current and historical
- Cost trend — daily/weekly/monthly comparison
- Forecast — projected monthly amount based on current consumption
- Policy alerts — configurable thresholds that notify on over/underspend
Finance and engineering can identify spend drivers without knowing the underlying infrastructure billing mechanics.
Dedicated vs. shared capacity
| Model | Billing |
|---|---|
| Shared pool (default) | Usage-based per the formula above |
| Dedicated bare-metal | Fixed monthly base fee for reserved hardware + usage |
Dedicated capacity provides full resource guarantees and makes sense for workloads with strict performance or compliance requirements.
Questions or ready to get started?
Talk to us