CUBRID License Policy

Unlike other opensource DBMS vendors, CUBRID has no commercial license but only an opensource license in order to provide excellent cost savings to companies. Because of this unique license policy, customers are not required to open the source code of applications or to purchase commercial license.

CUBRID has a separate license for server engine and interface. The server engine adopts the GPL v2 or later license, which allows distribution, modification, and acquisition of source. The interface and tools has the BSD license in which there is no obligation of opening derivative works. The reason of adopting two separate license systems is that we do not want to give any limitations to independent software vendors (ISV) for developing and distributing various CUBRID based applications.

CUBRID License Structure

Benefits of CUBRID License Model

Features of CUBRID License

Library Link

I want to create an installable bulletin board. As a DBMS interface, I am using JDBC. If I want to distribute to others the bulletin board I created, should I open my source code?

I want to develop and sell an electronic payment system for small and medium-sized businesses. If I choose to use CUBRID as DBMS, should I open my product source code or purchase the commercial license?

Among various methods of using DBMS, the two examples show cases where you want to link various libraries and drivers provided by DBMS in your application. To use DBMS features, a JAVA application should be linked to the JDBC driver; a PHP application should be linked to the PHP interface, and so on.

If you want to use DBMS with the GPL license model, you should open the entire source code of the linked application. If a DBMS vendor sells a commercial license as a dual license policy, you do not have to open the source code by purchasing the commercial license. MySQL adopts this kind of license model.

GPL-based only DBMS: You should open your application's source code or purchase the commercial license (in case of a dual license policy).

CUBRID applies the BSD license to all the interfaces linked to applications, so you do not have to open the source code of your application when using CUBRID as your back-end database system.

CUBRID: No obligation to open the source code.

Simple Calling

I want to develop a DBMS backup management system. If it is useful, I want to sell it as a package. Because it is a backup management system, it just processes DBMS backup files or calls utilities without linking to the DBMS interfaces or libraries. Is the license still an issue for this case?

This is the case when the application simply calls DBMS interfaces or libraries without directly linking to them. However, if GPL-based DBMS is used, you should still open the source codes of your application just as when you link libraries.

GPL-based only DBMS: You should open your application's source code or purchase the commercial license (in case of a dual license policy).

CUBRID: No obligation to open the source code.

Distribution between Corporations

Our headquarter is located in USA, and we have local branches in Japan, China, and Korea. Can those branches provide services by using the games created by our headquarter?

When distributing an application created by DBMS with the GPL license to branch companies, you should open the source code of the application or purchase a commercial license. CUBRID provides the most competitive license model with companies or solution vendors that plan to enter into global markets.

GPL-based only DBMS: You should open your application's source code or purchase the commercial license (in case of a dual license policy).

CUBRID: No obligation to open the source code.

Interface Modification

It is inconvenient because the PHP interface in DBMS does not provide dynamic SQL features. If I modify and use the PHP interface, should I open the modified interface or a linked application?

In case of the GPL license, if the source code is modified, the source should be opened, and the improved function should be shared among other users. However, in case of the BSD license, it is not necessary to open the modified source when it is used for either individual or commercial purpose.

GPL-based only DBMS: You should open your application's source code or purchase the commercial license (in case of a dual license policy).

CUBRID: No obligation to open the source code.

We have reviewed the benefits of CUBRID License Model in four scenarios. The benefits for market players such as developers, independent software vendors, and companies are briefly summarized below:

Developer: A developer can modify or distribute interfaces without limitations and save license cost when developing a commercial application program.

Independent software vendor : A vendor can save total solution cost (solution + DBMS), and it can distribute and sell its source code freely without an obligation of opening the source code.

Company: A company can save Total Cost of Ownership (TCO) dramatically and customize software for their requirements.

Limitations of CUBRID License Model

In our company system, the "organization chart" should be included in all pages. Because of frequent organization changes, recursive queries are indispensable. If I add this feature to the DBMS engine, should I open the modified DBMS code and our company system?

The DBMS engine is a core infrastructure for software development, so it is considered proper to share improved features with many other users. To share the improved features of CUBRID server engine, the database server adopted the GPL license. Therefore, if you modify the database server engine, you should open the modification to other users.

GPL-based only DBMS: You should open your application's source code or purchase the commercial license (in case of a dual license policy).