Watch Units

Problem

All queries consume a different amount of resources. Some queries require 100 records to get results, while others go through thousands or millions of records. This creates a situation where we provide a user-friendly data retrieval format, but because of the varying complexity of the queries, it becomes difficult for us to generate adequate pricing for our product.

When we were working on a solution, our first instinct was to look at the problem as a whole and come up with some sort of transparent, simple pricing system.

Solution

After some thought and research, we came up with something that combines simplicity and fairness, but also adapts to whatever your needs are. We think itโ€™s going to be a huge win for everyone involved.

So hereโ€™s how it works:

Watch Units for all our methods have been calculated in advance. When you interact with our API you wonโ€™t encounter the fact that you may be recalculated units in real time. That means that you donโ€™t need to worry about sudden changes in your cost structure.

The best part? Itโ€™s totally transparent! Youโ€™ll always know exactly what youโ€™re paying for and have full control over your spending.

Whatโ€™s more, this system will incentivize query optimization, which means everyone wins โ€” from us to you to the people who are using your data (like your customers).

Weโ€™ve also got some rewards in the works to incentivize certain tasks (like optimizing queries) so you can get even more out of our platform than ever before. Weโ€™ve been working hard to make sure our service isnโ€™t just user-friendly and effective โ€” itโ€™s fun too!

Last updated