Billing

Introduction

Quix is billed in real-time using pre-purchased credits which are either included in your subscription (Tier Credits) or purchased separately (Purchased Credits).

Your account must have a positive credit balance to be operational.

Quix is usage-based so you’ll burn-down against your positive credit balance only when consuming resources in your solution; this means you will never pay for idle resources.

Billing cycle

Quix billing operates on a monthly cycle starting and ending at the date and time that you register for an account.

Billing page

Details of your consumption (per account and per resource) will be available on your billing page inside the portal.

This is a live view that will be precise when viewed and always up to date.

You can monitor consumption, purchase additional credits and - eventually - upgrade your subscription from this page.

Credits

To pay for Quix you have to pre-purchase Credits which can be spent on any billable resource needed to stream, process and store data.

The base rate for 1 credit is currently $0.10.

You can see an itemised list of resource costs on the pricing page of our website here.

Tier Credits

A fixed allowance of Tier credits is included in your monthly subscription.

Just like the data plan on your cell phone, unused Tier Credits expire at the end of your billing cycle to be replaced with a fresh allowance.

To ensure you get maximum value from your subscription, Tier Credits are always consumed before Purchased Credits.

Purchased Credits

You can purchase additional credits using a credit card or bank balance transfer. We’re working to integrate a payment system; in the meantime, please get in touch with us to make a manual payment.

Unlike Tier Credits, Purchased Credits do not expire each month. Any unused credits will roll-over for a maximum of 12 months from the time and date that you purchased them, at which point they will expire.

Running out of credits?

We’ll send you an email if we predict you’ll run out of credits during the current billing cycle.

At this point you can purchase additional credits to keep your solution running.

If money is tight then please let us know what you’re working on; we’d love to hear your feedback and could potentially add some free credits to your account if you’re doing something interesting, a student, startup or charity.

Out of credits?

If you do nothing and run out of credits then we’ll keep your data and projects safe but pause your deployments, topics and catalogue until your billing cycle renews or you purchase credits.

We’ll reactive everything when your credit balance is positive again, at which point you can restart your models and services manually.

Any overspend from one billing cycle - typically for consuming data storage resources whilst your solutions are paused - will be deducted from the following one.

Billable resources

Quix credits are spent against billable resources, which currently include:

Workspaces

The container for each one of your apps, products or services. A workspace is a full data platform with all the features of Quix encrypted and authenticated in a sandboxed environment.

Workspace are very durable resources so we priced them per item-month. But we bill them per nanosecond, so if you only create one for an hour then you’ll only pay for the hour.

Topics

The backbone of your solutions. Topics group data streams and allow you to build data-driven applications and ML pipelines by combining them with models and services, using the pub/sub pattern.

Topics are also very durable so we priced them per item-month. But we bill them per nanosecond as you’ll probably create and delete a lot of them in the development process.

Data streamed

Any data that is streamed in a topic.

All data is priced per GB regardless of the type, volume or velocity, and billed per byte to keep things accurate.

Catalogue reads & writes

If you select topic persistence, you will be charged to write the data streamed in that topic to the catalogue.

If you use the Catalogue API to query historic data, you will be charged to read data from the catalogue.

Priced per GB and billed per byte.

Catalogue API

If you use the Catalogue API to make an analytic query on historic data - like an aggregation - then you will be charged the time it takes to compute the query (the query time).

This will be an additional charge to any Catalogue read charges incurred to get the query data from the catalogue.

Priced per minute and billed per nanosecond.

Catalogue storage

If you select topic persistence, you will permanently store data in the catalogue.

Priced per GB/month and billed per byte/nanosecond.

Compute CPU

Projects deployed to Quix serverless compute environment will consume CPU.

The charges are tiny so we priced per core/hour, but we bill per millicore/nanosecond so you only pay for exactly what you use.

Compute memory

Projects deployed to Quix serverless compute environment will consume memory.

The charges are tiny so we priced per MB/hour, but we bill per Byte/nanosecond to be accurate.

Stream Reader API & Stream Writer API

Used to write/read data to/from topics from external systems.

Priced per GB streamed and billed per byte streamed.