Prices and Billing

Current Prices

Billable Usage Unit Price
Data Storage (GiB Month) $0.03 USD
Network Ingress (GiB) $0.01 USD
Network Egress (GiB) $0.10 USD
List Chunks (1M Ops) $0.03 USD
Get Chunks (10k Ops) $0.12 USD
Put Chunks (10k Ops) $0.12 USD
Provisioned Repository (Day) $0.10 USD

How your bill is calculated

We meter and periodically aggregate customer usage, this means means your invoice depends on your data upload and access patterns. An idle repository will always incur the minimum 'Provisioned Repository Fee' of $0.10 cents per day, or approximately $3.00 a month.

For a discussion of prices and how your usage might affect this see the price table and feel free to contact for help.

Note that on occasion usage reporting may be delayed by up to a few days due to the inherent challenges of tracking and aggregating large amounts of data access.

Billable Units

Provisioned Repository Days

You are charged a fixed daily fee for every bupstash repository you have provisioned. For the purpose of billing, a month is approximated as 30 days, so a single repository will always be at least $3.00 a month.

Data Storage

You are charged proportionally to the number of GiB of data stored in your bupstash repository each month.

Network Ingress

You are charged for each GiB of data uploaded to our servers, note that this includes all bupstash and ssh protocol traffic.

Network Egress

You are charged for each GiB of data downloaded from our servers, note that this includes all bupstash and ssh protocol traffic.

Chunk Operations

Bupstash splits all uploaded data into chunks of data (usually between one to eight megabytes each, and at least one per directory uploaded), these chunks are the unit of data storage and deduplication. You are billed for chunk operations that occur in your bupstash repositories. Uploading data uses 'Put Chunk' operations, downloading data uses 'Get Chunk' operations and things like bupstash garbage collection use 'List Chunk' operations. Feel free to contact or the community chat for further clarification. Technical users can review the bupstash source code to see how chunks are processed internally.

Tips for Avoiding a Large Bill

Gradually ramp up your usage so you can understand your usage patterns and better predict what your costs will be.

Review your spending hold trigger in the account and billing menu, this is not a hard limit, but is helpful in avoiding over spending.

We strongly recommend using a separate bupstash 'send-log' for each periodic upload, this can dramatically reduce upload costs as bupstash will be able to remember data it sent during the last upload.

Due to cloud bandwidth prices, backup restores are one of the most expensive aspects of, be aware of how much an emergency full backup restore would cost and factor that into your budget. Partial restores are often possible saving both time and bandwidth.