Pricing and Billing
Last updated
Was this helpful?
Last updated
Was this helpful?
When you sign up, you get $10 in free credits so that you can start getting acquainted with the platform.
TileDB Cloud charges in three ways:
$0.11 / CPU / hour for a task time: This is the time it takes for a task from beginning to completion. Depending on the task and user parameters (see , and ), the number of CPUs used will be different. This price of $0.11 per CPU-hour is based on 1 CPU usage. The time is multiplied by the number of CPUs used in the task. At the end of the month, usage is summed up and rounded to the nearest second.
$0.14 / GB of data egress: This is the amount of data retrieved from the service to your client, not the data processed by a query. Egress is summed up and rounded to the GB at the end of the month.
$0.06 / CPU / hour for the notebook server duration: Notebooks are charged for how long the server is running and based on the size of the server. See for the instance types along with the number of CPUs for each type.
In TileDB Cloud you need to register your own data, which you must currently store in your own cloud buckets. TileDB Cloud does not offer storage hosting. You just your already existing cloud-stored arrays (created with ), and TileDB Cloud manages access and computation on those arrays without unnecessary copying and movement of the data.
All access via the web console, excluding notebook usage, is free and no charges are applied. TileDB Cloud bills you monthly.
Suppose you run a UDF which takes five minutes and returns no data to your client outside TileDB Cloud. Assume also that the UDF uses 2 CPUs. You will then be charged:
Query time: (5 / 60) hours * 2 CPUs * $0.11 per CPU-hour = $0.0183
Data retrieved: $0.00
Total: $0.02
If you do not belong to any organization, then all charges (array access, UDF, SQL, notebooks) are directed to your personal account. If you belong to one or more organizations, the following rules apply:
For SQL, UDFs and notebooks , TileDB Cloud charges the user's first organization (the one the user joined first).
For array access, TileDB Cloud determines how the user got access to the array. Suppose the user is called user
and belongs to one or more organizations, but the "first" is called org
. Here are the possible scenarios:
Array owned by user
-> user
is charged.
Array owned by org
-> org
is charged
Array owned by another organization org2
, shared with org
-> org
is charged
Array owned by org2
, shared with org
AND shared with user
directly -> Error unless
Default namespace to charge
is configured (see below)
Array owned by another user user2
(not an organization) -> user
is charged
TileDB Cloud also allows you to specify explicitly who to charge:
In your profile Settings
, there is a field called Default namespace to charge
.
Every programmatic request has a namespace
argument that allows you to specify the account to charge (e.g., see ).