Storage, networking, and service prices
Rates for persistent data, recovery copies, buckets, traffic, addresses, and operational retention.
Service meters charge retained capacity, traffic, or an allocated network service independently of guest execution. Open Organization → Billing → Pricing → Services for the rate card and inspect a resource's Usage tab for its meter.
Persistent volumes and recovery data
Persistent storage and recovery data use these capacity meters:
| Service | Per GiB per 730-hour month | Billed capacity |
|---|---|---|
| Local NVMe volume | $0.025 | Provisioned logical size |
| Replicated NVMe volume | $0.040 | Provisioned size; three storage replicas included |
| Performance replicated NVMe | $0.070 | Provisioned size; three replicas and the published performance-class policy included |
| Snapshot-exclusive retained blocks | $0.012 | Blocks needed only by retained snapshots or clones |
| Managed backup archive | $0.006 | Retained stored backup data after supported compression and deduplication |
| Private imported images | $0.006 | Stored image data |
The replicated rate is per logical GiB, not three times that amount. Encryption and ordinary I/O operations are included; supported IOPS or throughput caps have no separate control fee. The selected class and pool still determine actual performance and admission limits.
Snapshots do not charge live-volume shared blocks again. Blocks needed only by retained snapshots or clones use the snapshot meter once, regardless of the number of references to the same retained block. Different independent backup copies are separate retained data.
Managed backups include their internal object request operations. Verification or restore-test guests and temporary volumes use ordinary compute and storage rates while they exist. External archive providers charge their own storage and requests; Infra adds no per-job orchestration fee.
A regional replication target uses its ordinary provisioned volume rate. Copied bytes incur the cross-region transfer rate; retained checkpoints follow snapshot accounting. There is no separate per-relationship license fee.
Application object buckets
Object storage is $0.006/GiB per 730-hour month. A million write, list, or multipart management requests cost $0.20; a million GET or HEAD requests cost $0.05. Delete requests and multipart abort requests are free. Charges are proportional to actual request counts rather than whole-million minimums.
Noncurrent versions, retained uploads, and locked objects consume storage until eligible removal. Managed backup workers do not pay application-bucket request fees again for data already on the managed-backup meter.
Data transfer
Inbound traffic and private traffic within the same region are free. Each organization receives 1,024 GiB of internet outbound transfer per calendar month, pooled across its eligible hosted resources. Unused allowance does not carry forward. Additional internet outbound is $0.005/GiB.
Cross-region private transfer is $0.003/GiB, charged at the source once. It does not also consume internet allowance. The same rule applies to initial replication copies and subsequent changed data. Destination ingress is not charged again.
A byte is classified by its actual path. Downloading a snapshot or bucket object to an internet client uses internet outbound; copying it through a supported private regional path uses that path's rate. Retrying a real data transfer can send additional billable bytes.
Addresses and managed networking
Managed networking uses these time-based rates and address inclusions:
| Resource | 730-hour month | Included allocation |
|---|---|---|
| First IPv4 on a running droplet | $0 | One assigned address |
| Extra, detached, or stopped-target IPv4 | $1 | Per retained address |
| IPv6 allocation | $0 | Within regional prefix limits |
| Single-instance load balancer | $3 | L4/L7 listeners and one IPv4 |
| Redundant load balancer | $6 | Supported redundant mode and one service IPv4 |
| Single egress gateway | $3 | One egress IPv4 |
| Redundant egress gateway | $6 | Supported redundant mode and one service IPv4 |
| Private-circuit attachment | $10 | Infra attachment management; carrier and physical circuit charges are separate |
Network services are metered by allocated time. A service-included address is not billed again as a standalone IPv4 while that inclusion applies. Additional addresses follow the ordinary extra-address rate. Internet transfer uses the pooled rate without another balancer or gateway processing charge per GiB.
VPC segmentation, managed peering, baseline edge DDoS protection, private routes, firewall rules, and certificate installation have no separate resource fee. Private connectivity still uses its actual circuit and transfer terms.
DNS and health-based failover
The first 10 managed zones and 1 million authoritative queries per month are included per organization. Additional zones are $0.20 per zone per 730-hour month; additional queries are $0.10 per million, prorated by actual count.
The first 10 DNS health checks are included. Additional checks are $0.10 per check per 730-hour month. Applying a failover policy has no separate fee. Load-balancer backend health probes do not count as DNS health checks.
Metrics, logs, recordings, and artifacts
Standard metric collection, query APIs, alert evaluation, audit functionality, and automation are included. The hosted default retention is 7 days raw metrics, 365 days aggregates, 30 days ordinary logs, 365 days audit, and 30 days supported session recordings, subject to configured policy.
The organization includes 10 GiB of retained logs, recordings, and audit-export artifacts. Additional retained capacity is $0.010/GiB per 730-hour month. There is no separate query or playback-request fee; internet downloads use ordinary transfer. Temporary restore compute and independent archive copies retain their own meters.
Private images and general object artifacts use their storage meters, not the observability allowance. Data is not billed under two storage classes for the same managed copy. Externally supplied KMS, log collectors, licensing, and carrier services can charge independently.
Retained resources and removal
Rates continue while a billable resource or retained data remains. A stopped droplet can keep volumes and addresses; a deleted source can leave snapshots, backups, recordings, or held archives. Provider locks can delay deletion.
Inspect Organization → Usage → Retained resources before closing a project. Cleanup operations report actual retained references; submitting deletion does not mean storage was reclaimed. See retention, space accounting, and billing examples.