Frequently Asked Questions

What is the licensing model for Dragonfly? Is it open source?

Dragonfly is released under BSL 1.1 (Business Source License). We believe that a BSL license is more permissive than AGPL-like licenses. In general terms, it means that dragonfly’s code is free to use and free to change as long as you do not sell services directly related to dragonfly or in-memory datastores. We followed the model set by other companies like Elastic, Redis, MongoDB, Cockroach labs, Redpanda Data to protect our rights to provide service and support for the software we are building.

Can I use Dragonfly in production?

License wise you are free to use dragonfly in production as long as you do not provide dragonfly as a managed service. If you would like help from the DragonflyDB team in getting up and running, you may apply for our free Early Access Program.

How does Dragonfly’s vertical scaling compare to a Redis cluster?

Dragonfly utilizes the underlying hardware in an optimal way. This means that it can run on small 8GB instances and scale vertically to large 768GB machines with 64 cores. This versatility allows for far less complexity as well as lower infrastructure costs when compared to running cluster workloads. In addition, Redis cluster-mode imposes some limitations on multi-key and transactional operations while Dragonfly provides the same semantics as a single node Redis.

When will you support X command?

You can check our command reference pages to see which commands are already supported. Dragonfly has implemented more than 200 Redis commands which we think represents good coverage for the vast majority of use cases. Having said that, if you require commands that are not supported, please feel free to open an issue or vote on an existing issue. We will do our best to prioritise those commands according to their popularity.