The Seven Bridges Knowledge Center

The Seven Bridges Platform is a simple solution for doing bioinformatics at industrial scale. But sometimes, everyone needs a little help.

Get Started    What's new?

Cloud infrastructure pricing

Overview

Cloud infrastructure costs on the Seven Bridges Platform are based off of task execution and Platform file storage.

When you run a task on the Seven Bridges Platform, we use one or more compute instances from the Platform's underlying cloud infrastructure provider to process the data. Also, when you add your own files to the Platform and put them in a project, they are housed in cloud storage. Therefore, there are two types of costs you are billed for per month:

  • Compute costs
  • Storage costs

To see the relevant information on compute and storage costs, you should know which cloud infrastructure provider you run the Seven Bridges Platform on: Amazon Web Services in the US (AWS US East); Amazon Web Services in Frankfurt, Germany (AWS EU) or Google Cloud Platform. If you didn't choose a cloud provider when you signed up for the Platform, you will be using AWS US East.


If you signed up from early 2016, you will have had the option to select your cloud provider from AWS and Google Cloud Platform. If you signed up from early 2017, you will have had the additional option to select AWS EU as your cloud provider.

About compute costs

Compute costs depend on your cloud infrastructure provider. If you use the Platform with Amazon Web Services (AWS) as your cloud provider, Elastic Compute Cloud (EC2) instances are used to perform computation tasks. If you use the Platform with Google Cloud Platform as your cloud provider, Google Compute Engine instances are used to perform the computation tasks. In both cases, Seven Bridges passes through compute instance costs with no extra charge or fee for accessing the cloud services through the Platform.

The following table shows the compute services and charging units per cloud provider:

Cloud service provider
Service name
Charging unit

AWS US East and AWS EU

EC2

per Second

AWS US East and AWS EU

EBS (if applicable)

per Second

Google Cloud Platform

Google Compute Engine

per Second (minimum 1 minute + 1 second increments)

Google Cloud Platform

Persistent SSD disk

per Second

Compute Costs: Amazon Web Services

If you run the Platform using AWS as your cloud infrastructure provider, the Platform performs computation tasks using Amazon EC2 virtual computing environments, known as instances. There are various types of instances that have different configurations of CPU, memory, storage and networking capacity. See the list of AWS instances used on the Seven Bridges Platform on AWS US East and AWS EU.

AWS charges for the use of their compute instances on a per second basis, but the rate depends on the AWS pricing model. The Platform uses two AWS pricing models:

  • On-Demand: you pay for compute capacity at a fixed hourly rate. This is the Platform default.
  • Spot: the hourly rate is dictated by the market (supply and demand) for AWS EC2 spare compute capacity.

All public workflows on the Platform are set up to use instances that offer the optimal ratio of On-Demand price and compute power, while you are also able to perform optimization for your applications that you want to use on the Seven Bridges Platform.

Amazon EC2 On-Demand instances

By default, the Platform uses instances priced using the On-Demand model.

The rate of On-Demand instances depends on the instance type used and is shown in the following price list (select US East (N. Virginia) or EU (Frankfurt) from the Region dropdown menu based on the cloud infrastructure provider on which you run the Seven Bridges Platform). AWS expresses all rates per hour, but the calculation of the price is done on a per-second basis: the per-hour price is divided by 3600 and then multiplied by the actual number of seconds the instance was running.

Amazon EC2 Spot Instances

When your task runs using Spot Instances, you get charged the current market price for that instance for the time period the instance was running. AWS expresses all rates per hour, but the calculation of the price is done on a per-second basis: the per-hour price is divided by 3600 and then multiplied by the actual number of seconds the instance was running.

The maximum hourly price that you will be charged for an instance is the bid price of that instance. Because the bid price used by the Platform is the On-Demand price for that particular instance, you will never pay more than the On-Demand hourly rate for an instance you're using.

If the market price of a Spot Instance you're using exceeds the bid price (i.e. the On-Demand price for that instance type), the Spot Instance is terminated and the the task will continue running on an On-Demand instance(s). If spot instance termination occurs during the first hour of running the task on the instance, you will not be charged for using the spot instance. However, if the spot instance is terminated at any point after the first 60 minutes, you will be charged for the entire number of seconds the instance was running.

Amazon EBS

Amazon EBS volumes are storage volumes that can be attached to compute instances to provide additional space for file storage while files are being used in computation tasks. EBS volumes can be attached to the following types of instances:

  • Instances that do not include any storage space (EBS-only instances), such as c4 and m4 instances. EBS storage is mandatory for these instances and you can define any size from 2 GB to 4096 GB depending on your task's storage requirements during computation.
  • Instances that already include storage space, in order to increase the available storage on the computation instance. In this case, the instance storage is completely replaced by the attached EBS storage, up to the maximum of 4096 GB. The option to increase storage size for instances with their own storage is especially convenient for bioinformatics workflows as the files that are used as inputs for computation tasks and the files produced as results can be very large.

EBS is billed on a per second basis, while AWS expresses charges for EBS disk space in GB*hour/month. Please note that Seven Bridges passes through EBS storage costs with no extra charge or fee for accessing AWS services through the Platform.

Cost example

Learn more about how EBS is charged from the example below. Note that the example only serves as an illustration of how EBS costs are calculated. For current EBS prices, refer to the official Amazon EBS pricing chart. Make sure to select US East (N. Virginia) or EU (Frankfurt) from the Region dropdown menu.

Running RNA-seq Alignment - TopHat on a c4.2xlarge instance with 1TB of EBS:

  • c4.2xlarge = 8 CPUs, 15GB RAM (EBS Only) at $0.44 per Hour
  • Additional 1TB of EBS disk space at ~$0.10 per GB*hour/month

Assuming that the workflow took 14 hours and 25 minutes (51900 seconds) to complete:

  • c4.2xlarge x 14h25m = $6.34
  • 1TB EBS x 14h25m = ($0.10 per GB*hour/month * 1024 GB * 51900 seconds) / (3600 seconds/hour * 24 hours/day * 30 days/month) = $2.05

Compute Costs: Google Cloud Platform

Google Compute Engine

The Google Cloud Platform (GCP) offers a range of compute instances that can be used to run computation tasks. If you are using GCP as the cloud infrastructure provider, you will be able to select from n1-standard, n1-highmem and n1-highcpu instances to run tasks on the the Seven Bridges Platform. The full list of GCP instances that can be used on the Platform is available on this page.

The use of Google Cloud platform is charged on a per second basis. All instances are charged for a minimum of 1 minute. After the initial minute, instances are charged in 1 second increments.

Google SSD persistent disks

Google Cloud Platform instances come without any integrated storage, so they need to have defined attached storage. If you run the Platform using GCP as the cloud infrastructure provider, SSD persistent disks are used as attached storage for computation instances, during execution of computation tasks. You are able to configure the attached storage size using the sbg:GoogleInstanceType hint. The size of attached storage can be from 2 GB to 4096 GB.

Cost example

Learn more about how Google SSD persistent disks are charged from the example below. Note that the example only serves as an illustration of how costs are calculated. For current and detailed information and pricing, please refer to the official GCP documentation on persistent disks.

Running RNA-seq Alignment - TopHat on an n1-standard-4 instance with 1TB of attached persistent SSD storage:

  • n1-standard-4 = 4 CPUs, 15GB RAM at $0.19 per Hour
  • Additional 1TB SSD persistent disk at $0.17 per GB-month

Assuming that the workflow took 14 hours and 25 minutes (51900 seconds) to complete:

  • n1-standard-4 x 14h 25m = $2.74
  • 1TB persistent SSD x 14h 25m = ($0.17 per GB*hour/month * 1024 GB * 51900 seconds) / (3600 seconds/hour * 24 hours/day * 30 day-month) = $3.48

Storage Costs

Storage is billed for all files that belong to your projects. This includes the files you upload to the Platform and files that are produced as results of analyses. If you run the Platform with AWS as your cloud infrastructure provider, the storage service is Amazon Simple Storage Service (Amazon S3). If your cloud infrastructure provider is GCP, your storage service is Google Cloud Storage (GCS).

Cloud service provider
Service name
Charging unit

Amazon Web Services
(AWS US East and AWS EU)

Amazon Simple Storage Service (S3)

per GB-Month

Google Cloud Platform

Google Cloud Storage

per GB-Month

Please keep in mind that file storage is not charged twice for the same file. If a file is present in more than one of your projects that belong to one billing group, storage will be charged only once. When we calculate your monthly storage cost, we collect all files across all projects belonging to a single billing group, and then bill only once for each individual file within that billing group. A file is billed once regardless of which project it was uploaded to or how many times it was copied across any number of projects.

However, note the following scenarios in which we actually do bill for multiple appearances of a single file:

  • When a file is copied to a project belonging to a different billing group: in this scenario, both billing groups are treated as "owning" a file, and both will pay for one copy. Again, each billing group may have multiple copies of that file in any number of projects, and will only pay once.
  • When a file is re-uploaded: we do not detect for content equality, so if you upload the same file twice, the Platform sees (and bills for) two different files.
  • When a file is archived and restored: restoring a file is considered as creating a temporary copy that can be worked on. While a file is restored, we bill both for keeping the archived copy and the one in active storage that can be used as input.

You are not charged for storing public files from our Public reference files repository or from our public datasets when you copy them into your project. However, you are responsible for the costs of any files derived from processing these public files. For instance, if you remap reads, you are charged for the storage of the resulting BAM files.

Sample storage cost calculation

Please note that the calculation is for information purposes only and is made according to the prices at the time of writing this page. To find out the current prices, visit the following pages depending on the cloud provider:

  • Amazon S3. Make sure to select US East (N. Virginia) or EU (Frankfurt) from the Region dropdown menu, depending on the Amazon region you run the Seven Bridges Platform on.

  • Google Cloud Storage.

As shown in the table above, both cloud providers charge for storage on a per GB per month basis. This example shows how the total number of GB per month is calculated, given that the amount of data stored is likely to vary during one month.

Assume you store 100 GB (107,374,182,400 bytes) of data for 15 days in March, and 100 TB (109,951,162,777,600 bytes) of data for the final 16 days in March.

At the end of March, you would have the following usage in Byte-Hours: Total Byte-Hour usage= [107,374,182,400 bytes x 15 days x 24 hours per day] + [109,951,162,777,600 bytes x 16 days x 24 hours per day] = 42,259,901,212,262,400 Byte-Hours.

Let’s convert this to GB-Months: 42,259,901,212,262,400 Byte-Hours / 1,073,741,824 bytes per GB / 744 hours per month = 52,900 GB-Months

Based on the calculated number of GB-Months, we will do cost calculation for both cloud providers.

Sample Calculation: Amazon Web Services

Amazon S3 storage has three pricing tiers depending on the amount of data stored. This is a calculation of the monthly cost based on the amount of GB-Months calculated above:

  • First 50 TB per month: 51,200 GB (50 x 1024) x $0.023 = $1,177.60
  • Next 450 TB per month: 1,700 GB (remainder) x $0.022 = $37.40
  • Over 500 TB per month: 0 GB = $0.00

Total Storage Cost = $1,177.60 + $37.40 + $0.00 = $1,215.00

Sample Calculation: Google Cloud Storage

This is the calculation for Google Cloud Storage:

  • 52,900 GB x $0.026 = $1375.40

Total Storage Cost = $1375.40

Cloud infrastructure pricing