Licensing Databend
Databend code is distributed under two licensing types:
Type | Description |
---|---|
Apache 2.0 License | Core features under the Apache License are free to use and fully open source. |
Elastic 2.0 License | * Elastic (Free) features are free to use. The source code is available to view and modify under Elastic 2.0 License Limitations. * Elastic (Paid) features require an Enterprise License key to access. The source code is available to view and modify under Elastic 2.0 License Limitations. |
Databend's core functionality is available for free usage. The majority of core features are licensed under the permissive Apache License. However, specific features located in the src/query/ee and src/meta/ee directories are governed by the more restrictive Elastic License.
For access to Databend Enterprise features, a paid license from Databend is required, and these features are also subject to the Elastic License. For additional custom licensing options, please feel free to contact us.
You can find the feature's license by taking a look on the code file's header under the Databend repository
The following topics cover how to obtain, set, and verify an enterprise or trial license to access the Enterprise Features.
Obtaining a License
All Databend code is included in the same binary. No license key is required to access Apache and Elastic (Free) features. To access Elastic (Paid) features, users have two options:
- An Enterprise license enables you to use Databend Enterprise features for longer periods (one year or more). To upgrade to Enterprise license, contact sales.
- A Trial license enables you to try out Databend for 15 days for free, contact us to get your trial license.
Databend Labs encourage non-commercial academic research involving Databend. For such projects, please contact us for possible long term licenses)
Setting a License
In the following example, we assume that you are the root
user. Then use the SET GLOBAL SETTING
command to set the license key:
SET GLOBAL enterprise_license='you enterprise license key';
Verifying a License
To verify a license, you could use admin procedure CALL
command to check organization name and expiry date info.
call admin$license_info();
+----------------+--------------+--------------------+----------------------------+----------------------------+---------------------------------------+
| license_issuer | license_type | organization | issued_at | expire_at | available_time_until_expiry |
+----------------+--------------+--------------------+----------------------------+----------------------------+---------------------------------------+
| databend | enterprise | databend | 2023-05-10 09:13:21.000000 | 2024-05-09 09:13:20.000000 | 11months 30days 2h 3m 31s 802ms 872us |
+----------------+--------------+--------------------+----------------------------+----------------------------+---------------------------------------+
License FAQs
If you have any other questions not covered below, please feel free to contact us.
Can I Host Databend as a Service for Internal Use at My Organization?
Yes, employees and contractors can use your internal Databend instance as a service under the Elastic license since it was created. Use of Enterprise features will always require a license.
Why Databend Choose Elastic License 2.0 for Enterprise Features?
The Elastic License 2.0 provides a good balance between open-source values and commercial interests.
Comparing other license such as Business Source License, Custom Community License, Elastic License 2.0 is simple, short and clear.
There only have three limitations applied:
- Cannot provide software as a hosted or managed service with substantial access to features/functionality.
- Cannot modify or circumvent license key functionality or remove/obscure protected functionality.
- Cannot alter/remove/licensing, copyright, or trademark notices of the licensor in the software.
I Would Like to Reuse Some Components From the Databend Project in My Own Software, Which Uses the Agpl or Another Open Source License, Is This Possible?
The Databend team is committed to supporting the open-source community and willing to consider extracting specific internal components that are generally useful as a separate project with its own license, for example, APL.
Can You Provide Some Examples Around What Qualifies as “Providing the Software to Third Parties as a Hosted or Managed Service” or Not?
I'm using databend for data dashboard on my analytic SaaS product
This is permitted under ELv2.
I'm an analytic engineer setting up Databend for my organization to use internally
This is permitted under ELv2, because you are not providing the software as a managed service.
I am a Managed Service Provider running Databend for my customers
If your customers do not access Databend. this is permitted under ELv2. If your customers do have access to substantial portions of functionality of Databend as part of your service, this may not be permitted.