Skip to content

Multi server license

Multi-server licenses are designed for teams that need to run Team Edition on more than one server.

Use cases

  • several independent environments (production, staging, test)
  • distributed infrastructure
  • high availability setups with standby servers

How it works

A multi-server license covers a fixed number of servers and named users under one subscription. All users must be listed in the license, even if only some of them connect to multiple servers.

Setup

To run a multi-server license, follow these steps:

  1. Install the product on each server where it should run.

  2. During installation, import the license key into each server. This key is the same for all servers in the subscription.

  3. Users synchronization

    • when the license is imported, the initial user list is pulled from the License Manager on dbeaver.com.
    • all servers share the same named users from License Manager.

    • users can also be added in three ways:

      • via License Manager
      • via the Team Edition UI
      • via SSO login (users are created automatically if seats are available)
      • via AWS IAM

  4. Changes in user management

    • updates from License Manager synchronize automatically once per hour.

      Tip

      To apply changes immediately, restart the server.

    • if a user is deleted or blocked in the UI, they can be re-added immediately through License Manager. The same action in the UI is only available after two weeks.

    Important

    License Manager always has the priority over all other user management methods.

  5. Offline work

    • multi-server licenses require internet access for automatic synchronization.
    • if a server has no internet connection, you must manually re-import the updated license file whenever the user list changes.

  6. Server configuration

    • multi-server subscriptions don’t require special configuration parameters. Servers work the same way as with single-server licenses.
    • each server can have its own domain, connections, and settings. The only shared element across servers is the licensed user list.

Multi-server license specifics

  • minimum of 3 users, at least one administrator required.

  • Can be deployed on-premise, in private or public clouds, or in hybrid environments.

    Info

    For details, see Deployment options.

  • supports different roles: administrator, developer, manager, editor, viewer.

    Info

    Learn more on Roles.

The number of users can be increased at any time during the subscription by sending a request by email or using the website. Additional users require an updated license. You can reduce the number of users, but only before the next renewal.

The number of servers can also be changed, but only by email request. As with users, servers can be reduced only before renewal.

Differences with single-server license

Aspect Single-server license Multi-server license
User management Managed fully inside the server admin panel. The license key is imported and updated in the UI. Main management through dbeaver.com. Users can also be added in the UI or via SSO if seats are available.
User list All users are named. Every user accessing the server must be counted in the license. All users must be named and counted in the license, even if not all connect to every server. One license key is shared across servers.
Synchronization Internet is not required. The server works offline and license updates are handled manually in the UI. Requires internet for automatic user synchronization, by default every hour. Without internet the license file must be reimported manually.
Offline mode Works offline without restrictions. Works offline only if the license file is manually reimported after user list changes. Without this, user updates will not apply.

Info

Learn more about license types.