RediSQL, fastest, simplest, in-memory SQL

We are on the mission to build the fastest and simplest, in-memory SQL engine. Join us on Github.

Go in-memory and forget SQL performance problems.

Based on Redis for optimal stability, reliability and performance.

  • 🚀

    RediSQL works mainly in memory, it can reach up to 130.000 transaction per second.

  • 📖

    RediSQL works with standard SQL, no weird dialects or new syntax to learn.

  • 👩‍🔧

    Just start Redis and load the RediSQL module.
    Simple to getting started

  • 👷‍♀️

    There are already binding available for most languanges, including python, go, javascript, ruby, php, rust and many more.
    Explore our tutorials.

  • 🎈

    RediSQL provides you with lightweight in-memory databases. It could completely shift your architecture. For example, you could create a new isolated database each day, one for each application tenant, or even one per user.

  • 💾

    While RediSQL focuses on in-memory database, it can also store data in a regular file. Of course this makes operations slower, but it allows RediSQL to reach a level of data persistency on par with incumbent databases such as Postgres or MySQL.

  • 📩

    With the ability to create several lightweight databases you could directly expose the databases to the end users instead of exposing an API that you would need to maintain. Just load all the data that the user may need into a RediSQL database, document the tables that are available, and give access to it to the users. They will write their own API without waiting on you.

  • 🚅

    RediSQL can also store results of queries into a Redis Streams. This allows different clients to consume part of the result, or to delay the consuption of a result. Moreover, it allows caching the result of expensive queries as Redis Streams to consume them over and over again.

  • 🔥

    JSON is the de-facto standard for sharing data between applications. RediSQL exploits the JSON1 module of SQLite to bring that capability to easy and quickly manage JSON data inside SQL statements and tables. In RediSQL you are able to manipulate JSON in every standard way.

  • 📄

    RediSQL fully supports also the FTS{3,4,5} engine from SQLite, giving you a full text engine at your fingertip. You will be able to manage and search for data.

All the code is released on Github. Engineers are free to explore the codebase, understand how it works, bend it to their use case and extract most of the value from it.
The simple build system in place will allow to quickly iterate on the code and fix eventual bugs.

Explore on Github

If you decide to purchase the PRO version, but for any reason it doesn't work for you, we will refund you. No question asked.

Purchase the PRO version

The open source version is and always will be free, for the PRO version we offers two different type of license. The regular license allow you to download each and every version of RediSQL anytime you wish, it renew annually.

The perpetual one which gives you the right to download one and only one version of RediSQL, it is a one time expense but it doesn't provide you with any updates. Also the support on the perpetual license is limited to one year.

Our users are impatient. They're probably distracted too. Keep it simple and beautiful, fun and functional. Clean aesthetics supported by a strong concept is what we stand for.

As many as you like, they have a very light memory overhead and you may actually improve performances running multiple databases in your instance since each database has its own thread of execution and you will get rid off most the waits for locks.

Yes it is possible to save the database on disk, however this will make the system slower. Of course, during RDB replication the database is serialized, compressed and saved on your Redis RDB file.

Yes you can, however this would be illegal and it would expose your company to legal risk, moreover you will lose the most valuable asset that comes with the PRO version which is the support. But, yes, we cannot do anything if you decide to go through that route.

It is faster and let us focus on what we do better, write software, instead of wasting our time in keeping up and running yet another ecommerce website. Yes, PayHip is safe and it use Stripe underneath.