Pricing

Details about TileDB Cloud Pricing

TileDB Cloud charges in two ways:

  • $1.80 / hour for the query time: This is the time it takes for a task from beginning to completion. Usage is summed up and rounded to the minute at the end of the month.

  • $0.14 / GB of data retrieved: This is the egress cost, i.e., 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.

Note that in TileDB Cloud you need to register your own data, which you must currently store in your own AWS S3 buckets. TileDB Cloud does not support storage hosting. You register your already existing S3-stored TileDB arrays, and TileDB enables access and computation on those arrays without unnecessary copying and movement of the data.

All access via the web console is free and no charges are applied. TileDB Cloud bills you monthly.

The TileDB Cloud pricing suggests that you should minimize the data you request at your client, and instead try to either perform UDFs that reduce the data, or write the data back to S3 (e.g., which can be done with both SQL as well as UDFs).

Example Pricing Scenarios

Reads
Writes
UDFs
SQL
Reads

Suppose you slice 3 GB from a TileDB array using TileDB Cloud and the read access takes 45 seconds. You will be charged:

  • Query time: (0.75 / 60) * $1.80 = $0.0225

  • Data retrieved: 3 * $0.14 = $0.42

  • Total: $0.0225 + $0.42 = $0.44

Writes

Suppose you write 256 MB to a TileDB array and the write request takes 20 seconds. You are charged:

  • Query time: (0.33 / 60) * $1.80 = $0.01

  • Data retrieved: 0 (see note below)

  • Total: $0.1

Each write may read back a fee bytes (e.g., for acknowledgements), thus incurring some minimal egress. This is added to the final billing but it is negligible as compared to the query time.

UDFs

Suppose you run a UDF on some TileDB array slice that takes 300 seconds, and returns only 1 MB of data to the user. You are charged:

  • Query time: (5 / 60) * $1.80 = $0.15

  • Data retrieved: (1 / 1024) * $0.14 = $0.00013

  • Total: $0.15 + $0.00013 = $0.15

Observe that you pay only for the 1 MB you retrieved (which is negligible), regardless of how many bytes the UDF processed. You can see here the benefit of the UDF reductions.

SQL

Suppose you run a SQL query on some TileDB array slice that takes 300 seconds. You are charged:

  • Query time: (5 / 60) * $1.80 = $0.15

  • Data retrieved: $0

  • Total: $0.15

Serverless SQL queries currently write the result directly back to S3 and, thus, there is no egress cost involved at all.

Our pricing is experimental. We are happy to get your feedback. You can also contact us if you need more free credits in case you are in a testing phase.