🐈
zeeSQL
  • zeeSQL, SQL and search by value for Redis. Fast, Simple and Reliable.
  • How to
    • How to choose between QUERY and EXEC
    • know-what-secondary-indexes-are defined
    • How to load zeeSQL in Redis
    • How to check if an index is used in zeeSQL and SQLite
    • know-what-secondary-indexes-are defined
    • create-an-index
    • create-a-view
    • create-a-secondary-index
    • How to create a trigger
    • quickly-ingest-data
    • How to copy a database
    • get-help
    • work-with-dates
    • using-full-text-search
    • work-with-json
    • How to create a new database in zeeSQL
    • How to create a new table in zeeSQL
    • know-what-tables-are-defined
    • know-what-databases-are-defined
    • works-with-boolean
    • How to get zeeSQL
    • How to get JSON output
    • add-multiple-rows
  • blog
    • node
      • Using RediSQL with Node.js
    • JSON on Redis via RediSQL, SQL steroids for Redis
    • golang
      • Using RediSQL with Go(lang)
    • Doubling the performances of RediSQL, SQL steroids for Redis.
    • zeeSQL now runs on SQLite 3.35
    • Query Redis on two attributes
    • RediSQL for analytics
    • Copying RediSQL databases
    • Release 0.9.0 of RediSQL, SQL steroids for Redis
    • Release 0.8.0 of RediSQL, SQL steroids for Redis
    • Release 0.7.0 of RediSQL, SQL steroids for Redis
    • JSON on Redis via RediSQL, SQL steroids for Redis
    • Release 0.6.0 of RediSQL, SQL steroids for Redis
    • python
      • using-redisql-with-python
    • Release 0.5.0 of RediSQL, SQL steroids for Redis
  • References
  • zeeSQL commits to backward compatibility
  • zeeSQL, a solid product for busy developer
  • zeeSQL and secondary indexes, how to search Redis key by value
  • Tutorial
  • Pricing for zeeSQL
  • Why you should migrate from RediSQL to zeeSQL
  • FAQs
  • Motivation
Powered by GitBook
On this page
  • How zeeSQL charges users
  • zeeSQL free plan
  • Getting a license
  • Example
  • Code examples
  • Pathological cases
  • Air gapped instances

Was this helpful?

Pricing for zeeSQL

zeeSQL is not a product free to run.

However, it comes with a generous free plan, so that small and medium applications can work without paying anything.

This document explains how the pricing for zeeSQL works.

It starts explaining how we charge for zeeSQL and then what is included in the free plan.

How zeeSQL charges users

zeeSQL uses a credit system linked to a license key.

In zeeSQL there are two main concepts, databases and secondary indexes.

Running either one (database or one secondary index) costs 1 credit every hour.

One credit costs 0,01€

We devise this pricing schema to scale on the complexity that zeeSQL is managing not on the size of your datasets.

There is an allowance of 2160 free credit each month for each license.

zeeSQL free plan

zeeSQL reports its usage (number of credit used) only if the user provided a license key.

It is not necessary to provide a license key to use zeeSQL.

However, without a license key, it is not possible to spend more than 3 credits each hour. This is enforced by avoiding creating a new database or a new index if you are already using 3 credits for an hour.

To spend more than 3 credits for an hour, you need to input a valid license key.

The 2160 free credit, are there to allow users to input a valid license while still benefit from the free plan.

3 credits each hours * 24 hours a day * 30 days a months = 2160 credit / month.

Which is exactly the amount of free credit available.

This will allow to test the system and do maintenance operations.

The 2160 credit/month can be spent also together during a single hour. This allows testing the product with multiple databases and secondary indexes.

The license can be shared between multiple zeeSQL processes.

Example

These examples show how much you will be charged for using zeeSQL.

They all assume steady-state operation where databases and secondary indexes are not generate or deleted.

Number of databases

Numbre of indexes

Credit usage

Cost per hour

Cost per month

1

0

1

FREE

FREE

3

0

3

FREE

FREE

4

0

4

0.01

7.20

5

0

5

0.02

14.40

1

2

3

FREE

FREE

1

3

4

0.01

7.20

2

3

5

0.02

14.40

2

4

6

0.03

21.60

Code examples

These code examples show what happens when the user tries to create more than 3 databases without one valid license key.

127.0.0.1:6379> ZEESQL.CREATE_DB DB_1
1) 1) "OK"
127.0.0.1:6379> ZEESQL.CREATE_DB DB_2
1) 1) "OK"
127.0.0.1:6379> ZEESQL.CREATE_DB DB_3
1) 1) "OK"
127.0.0.1:6379> ZEESQL.CREATE_DB DB_4
(error) Not enough credit in your license, please upgrade.
127.0.0.1:6379> ZEESQL.LICENSE SET $one_valid_license
OK
127.0.0.1:6379> ZEESQL.CREATE_DB DB_4
1) 1) "OK"

zeeSQL returns a simple error and does not allows the user to create more databases.

Similarly with secondary indexes.

127.0.0.1:6379> ZEESQL.CREATE_DB DB_1
1) 1) "OK"
127.0.0.1:6379> ZEESQL.INDEX DB_1 NEW TABLE users PREFIX users:* SCHEMA id INT name STRING
OK
127.0.0.1:6379> ZEESQL.INDEX DB_1 NEW TABLE games PREFIX games:* SCHEMA id INT game_name STRING player INT
OK
127.0.0.1:6379> ZEESQL.INDEX DB_1 NEW TABLE credit PREFIX credit:* SCHEMA user_id INT available_credits INT
(error) Not enough credit in your license, please upgrade.
127.0.0.1:6379> ZEESQL.LICENSE SET $one_valid_license
OK
127.0.0.1:6379> ZEESQL.INDEX DB_1 NEW TABLE credit PREFIX credit:* SCHEMA user_id INT available_credits INT
OK

Pathological cases

For instance, if you design your application to have one database for each user.

Air gapped instances

zeeSQL needs to communicate to a specific hostname to communicate how many credits each instance is using.

We can provide builds of zeeSQL that don't need to report back their usage.

PreviousTutorialNextWhy you should migrate from RediSQL to zeeSQL

Last updated 4 years ago

Was this helpful?

You can obtain a license from .

Please if your application is a pathological case.

If your system is without external connectivity, please .

Getting a license
this website
get in touch
get in touch