Enterprise

The price for object storage with SILO starts as low as $0.0036 per GB per month, with $0.0063 per GB for egress bandwidth.

The following table lists the types of metered services that appear in billing and usage user interfaces as well as invoices:

Metered Service Type	Metered Units	Increment	Pricing Unit	Price per Pricing Unit	Description
Object Storage	Bytes	GB Hour	GB Month	$0.0036 per GB Month	Storage is calculated based on bytes uploaded, including any encryption-based overhead
Egress Bandwidth	Bytes	GB	Total Volume	$0.0063 per GB	Bandwidth related to object downloads calculated on bytes downloaded including long tail elimination-related bandwidth
Segments	Segments	Segment Hour	Segment Month	$0.0000079 per Segment Month	Segments usage depends on storage. The default size for a segment is 64MB (or less), i.e., smaller objects use more segments

Billing is aggregated at the project level. A project is the SILO service construct used for aggregating usage, calculating billing, invoicing fees, and collecting payment. Billing on a project begins when a user upgrades to a pro account (even if their free trial has not ended). Projects are created by a single user, then multiple users may be added to a project team, and one user may be on more than one project. Within a project, usage is tracked at the bucket level and aggregated for invoicing to the project.

The following section describes how the charges listed in the table above are calculated to provide users with detailed insights into their cloud storage usage, broken down by storage, egress bandwidth, and the number of objects. Note that for billing purposes, usage data is continuously rolled up and aggregated. Billing data is not displayed in real-time in the SILO interface, and some time lag should be expected.

Object Storage​

Object storage is priced per GB per month in increments of byte hours. The calculation of object storage fees is based on a standard 720-hour month. Actual storage is metered in bytes uploaded. Bytes uploaded include the bytes associated with actual objects plus any nominal overhead associated with encryption. Byte hours are calculated based on the number of hours bytes are stored on the SILO Platform from when an object is uploaded to when it is deleted. The calculated number of bytes is then multiplied by the byte hour price. The byte hour price is derived from the GB month price divided by the standard 720-hour month and base 10 conversion of GB to bytes.

Example

A user uploads a 1TB file. Halfway through the month, the user deletes the file. With encryption overhead, the file is stored as 1.001TB. The 1.001TB is accounted for as 1,001,000,000,000 bytes. The file is stored for 360 hours. The file is stored for 360,360,000,000,000 byte hours. In this example, the price per GB month is $0.0036, and per GB hour is $0.000005. The price per byte hour is $0.000000000000005. The total amount charged for the storage is $1.80.

Bandwidth Fee​

Download bandwidth, also referred to as egress bandwidth, is priced per GB in increments of bytes downloaded. The calculation of download bandwidth price per byte is derived from the GB download bandwidth divided by the base 10 conversion of GB to bytes. The calculated number of bytes is then multiplied by the byte download bandwidth per byte price.

When an object is downloaded, several factors can impact the actual amount of bandwidth used. The download process includes requests for pieces from more than the minimum number of storage nodes required. While only a subset of pieces out of the total are required to reconstitute an object, SILO will try to retrieve an object from additional storage nodes to avoid potential long-tail performance lag from a single node.

Example

A user downloads one 1TB file. Based on the long tail elimination, up to 1.3TB of download bandwidth may be used. The 1.3TB of download bandwidth is accounted for as 1,300,000,000,000 bytes. In this example, the price per GB is $0.0063, and per byte is $0.000000045. The total amount charged for the egress is $8.19.

Per Segment Fee​

For most users and usage patterns, we do not expect a Per Segment Fee to be charged. Only when large numbers of segments are stored relative to a disproportionately small amount of data do we expect there to be a Per Segment Fee. Only use cases with large numbers of very small files or large numbers of very small multipart upload parts are expected to be subject to the Per Segment Fee.

Each segment stored on the network is charged a nominal Per Segment Fee. The Per Segment Fee is $0.0000079 per segment per month. Distributed object storage is optimized for large files (several MB or larger - the larger, the better). Very small objects generate more overhead with the storage of the metadata for the file than the actual storage of the object. Consequently, we charge a small Per Segment Fee to account for that overhead.

Examples:

• A single 1MB file is one segment.

• A single 10MB file is one segment.

• A single 64MB file is one segment.

• A single 256MB file is four 64MB segments.

• A single 1GB file is 16 segments.

Cost Example:

A user uploads 1.6 million one MB files, totaling 1.6TB. Halfway through the month, the files are deleted. The files are stored for 360 hours, accounting for 576,000,000 segment hours. The total cost for the segment fee would be $7.04.

Next Steps​

Explore more details about SILO pricing and features on our SILO Documentation. For assistance, visit the SILO Forum.