Billing
The Billing page shows your balance and the costs of your experiments, as well as containing tools for setting cost limits for your organisations, projects and org members.
Users are billed for usage of the following products within Strong Compute.
Container runtime
$1
per hour
Container GPU usage
$1.25
per GPU per hour
Cycle compute
$1
each cycle
Interruptible initialization
$18
each experiment
Interuptible compute
$1.25
per GPU per hour
Burst initialization
1¢
each experiment
Burst compute
TBA
based on cloud provider cost per GPU per hour.
Data transfer - local to bucket
9¢
per GB
Data transfer - bucket to local
9¢
per GB
Data bucket storage
2.47¢
per GB per month
Typical usage charges
Charges associated with typical usage patterns are as follows.
Working in container
Container runtime charged at US$1 per hour.
Container GPU usage charged at US$1.25 per GPU hour.
Cycle mode experiment
Cycle compute charged at US$1 per cycle.
Data transfer - local to bucket charged at 9¢ per GB for shipping data to Artifacts such as checkpoints.
Data bucket storage charged at 2.47¢ per GB per month for Artifacts such as checkpoints.
Data transfer - bucket to local charged at 9¢ per GB for downloading data such as checkpoint Artifacts to the local cluster.
Interruptible mode experiment
Interruptible initialization charged at US$18 per experiment.
Interruptible compute charged at US$1.25 per GPU per hour.
Data transfer - local to bucket charged at 9¢ per GB for shipping data to Artifacts such as checkpoints.
Data bucket storage charged at 2.47¢ per GB per month for Artifacts such as checkpoints.
Data transfer - bucket to local charged at 9¢ per GB for downloading data such as checkpoint Artifacts to the local cluster.
Burst mode experiment
Burst initialization charged at US1¢ per experiment.
Data transfer - bucket to local charged at 9¢ per GB for downloading Datasets to the burst cluster for training.
Burst compute charged the cloud provider rate per GPU per hour plus Strong Compute overhead.
Data transfer - local to bucket charged at 9¢ per GB for shipping data to Artifacts such as checkpoints.
Data bucket storage charged at 2.47¢ per GB per month for Artifacts such as checkpoints.
Data transfer - bucket to local charged at 9¢ per GB for downloading data such as checkpoint Artifacts to the local cluster.
Working in burst container
Data transfer - local to bucket charged at 9¢ per GB for shipping the user container from the container home cluster to a bucket.
Data transfer - bucket to local charged at 9¢ per GB for downloading the user container to the burst workstation.
Data transfer - bucket to local charged at 9¢ per GB for downloading a requested dataset for mounting to the container.
Burst compute charged the cloud provider rate per GPU per hour plus Strong Compute overhead for the burst workstation instance.
Data transfer - local to bucket charged at 9¢ per GB for data egress from the container.
Data transfer - local to bucket charged at 9¢ per GB for shipping the user container from the burst workstation to a bucket.
Data transfer - bucket to local charged at 9¢ per GB for downloading the user container to the container home cluster.
Note: charges for items that have not yet been finalized - such as Data bucket storage for Artifacts that are still being stored - appear on the Current Balance tab. When finalized - such as when an Artifact is deleted - these items will appear on the Billing History tab.
Current balance
The Current Balance page displays a summary of your Organisation's credit balance.
Current Balance: Your total credits minus your finalized charges.
Total Pending charges: Accrued charges for unfinalized line items.
Projected charges: Current balance plus total pending charges. This represents what your current balance would be if all pending charges were finalized at their current accrued amount.
Aggregate charges
Aggregate charges for your Organisation are show on the Billing History tab by product with Daily, Monthly, and Total usage.
Spending limits
This is where you can set limits on an organisation, user, or project level which cannot be exceeded even by an administrator of the organisation. When a limit is reached, all current and future experiments created that would exceed this limit will be cancelled, and a notice is displayed on the Experiments page advising users that a spending limit has been reached. Only an organisation’s Admin and Finance users can set and change spending limits for their organisation.
Statements
Coming soon.
Last updated
