Redivis offers a simple, predictable billing structure to pay for the associated costs in storing and querying your organization's data. Your organization will pay a flat rate, per month, for all data:
Unlike most other cloud environments, on Redivis you are not billed for researchers' queries or for the storage of data derivatives within their projects. These costs are instead captured via the "active" storage rate. With this model, your organization will only ever be charged based on the data it uploads, and neither you nor your researchers need to worry about creating runaway cloud bills.
Data storage costs are always pro-rated. For example, if you upload (or delete) a 100GB dataset halfway through the month, you will only be charged 50GB*mo for that dataset.
You can view your current usage and predicted costs on the Billing page of the administrator panel.
Dataset tables stored on Redivis are classified as active or inactive, depending on how recently researchers worked with data from that table. This allows organizations to realize substantial cost savings for seldom-used data, including historic versions of a dataset.
Active data is billed at $0.15/GB/mo, while inactive data is billed at $0.02/GB/mo.
All uploaded data begins as inactive. When a dataset table is "used", it will then become active. After 90 days of inactivity it will become inactive again automatically.
"Usage", as laid out below, applies both to the dataset table as well as any derivative tables in researchers' projects — that is, if a researcher creates an output table using your dataset, and then exports that table, any source tables for this output will become active.
The following actions count as usage and will reset the 90 day counter:
If your dataset contains multiple versions, data activity rules will always apply to specific versions of a table, allowing you to realize cost savings for historic versions of a dataset that are no longer in use.
Because Redivis stores an efficient row-level difference across versions, the active vs. inactive breakdown will reflect the size of the specific rows that are currently active.
For example, let's assume a dataset has one table: in
v1, it contains 1GB, and in
v2, we replace the data with another 1GB of records, of which half of them overlap with
v1. In this scenario, while each version of the table is 1GB, the total storage of the dataset is only 1.5GB, since we have 0.5GB of overlap between each version. If
v1becomes inactive (while
v2stays active), the 0.5GB of data unique to
v1will be marked as inactive, while 1GB of data will remain active.
Your organization will be granted between 10GB and 1TB of free storage, depending on its tier. For many organizations, they'll never exceed this limit, and won't need to manage storage-related costs. Savings from this free tier are first applied to active data, followed by inactive data.
In order to exceed the free storage limit, your organization will need to set up billing (see below). The free tier will still be taken into account when computing the bill — your organization will only be charged for storage above the free tier.
To set up up billing, navigate to the Payment settings tab. You can enter a credit card or contact us to change to invoiced billing.
To enable billing, provide the relevant information as well as an email address to send invoices. Your organization will automatically be billed on the first of every month.
You can view current and past invoices on the Invoices tab. You can double click on any of the listed invoices to view itemized details and make any necessary payments.
Invoices tied to a credit card will be automatically marked as paid. If your organization has opted for invoiced (net 30) billing, you must manually pay these invoices within 30 days. Click on the invoice item and follow the instructions for remitting payment.
View current and historic invoices on the "Invoices" tab of the billing panel
If any of your organization's data is stored in an external Google Cloud project (using custom data storage), you'll see another line item in the billing graph corresponding to the total amount of data in custom (non-Redivis) storage locations.
For data stored in custom locations, your organization will independently cover the cost of raw data storage directly through Google, and pay a reduced rate to Redivis for any active data.
Redivis does not charge data egress fees on data exports.
Redivis has an egress limit of 100 GB per user over a 30 day window. If you would like to remove that limit for your organization's data you can configure a GCP project to cover egress fees in your organization settings.