The server engine adopts the Apache License 2.0, which allows distribution, modification, and acquisition of the source code.

CUBRID APIs and GUI tools have the Berkeley Software Distribution license in which there is no obligation of opening derivative works.

The reason of adopting two separate license systems is to provide complete freedom to Independent software vendors (ISV) to develop and distribute CUBRID-based applications.

The CUBRID connection broker's main roles are: Also, a local object pool enables some parts of the execution to be deferred from the database server (e.g. tuple insertion and deletion, DDL statements), thus lowering the database server load.

Administrators can specify a list of server hosts each broker can connect to and, in the event of a failure of the master node, another will be used.

The implemented functions are ROW_NUMBER, COUNT, MIN, MAX, SUM, AVG, STDDEV_POP, STDDEV_SAMP, VAR_POP, VAR_SAMP, RANK, DENSE_RANK, LEAD, LAG and NTILE.

CUBRID optimizes the common scenario in web applications where database fields need to be incremented on certain events (e.g. page views).

Stored procedure code that requires database access must use the JDBC driver, either using the parent transaction or issuing a new one.

[9] The tool can be used in one of two modes: CUBRID's csql also implements some internal commands related to schema information, plan generation, debugging, transaction control, query timing and more.