Release Notes
You have successfully installed version 14.0.0 of the Gurobi Remote Services.
Gurobi Remote Services is a set of Gurobi features that allows a cluster of one or more machines to perform Gurobi computations on behalf of other machines. The key components of Remote Services are:
- Compute Server, which allows you to offload all Gurobi computations from a client machine onto a remote cluster.
- Distributed Workers, which can be used to perform parallel computation on multiple machines.
- The Cluster Manager, an application server that provides secured access to your Remote Services cluster, as well as providing a Web User Interface and a command-line tool that make it easier to manage and monitor your cluster. The Cluster Manager uses a database to store user accounts, API keys, jobs, batches, and settings. You can use Compute Servers without a Cluster Manager - we refer to that as a self-managed cluster. However, we recommended you use a Cluster Manager to get the rich set of features that it provides.
Please refer to the Gurobi Documentation for more details. All bug fixes listed by version can be found on our website.
Obtaining Your License
To manage your Gurobi licenses, you will need to visit the Gurobi User Portal. If you are a commercial user under maintenance, you should see your existing Gurobi licenses under the Licenses section. If you would like to request a free academic license or other licenses, you can do so from the Request License section. Once you have a license on the Gurobi User Portal, you will need to follow the instructions for installing or downloading a license by clicking on the Install or Open button next to your license.
Supported Platforms by the Compute Server/Cluster Manager
| Platform | Operating System | Notes |
|---|---|---|
| Windows 64-bit (win64) | Windows 10, 11, Windows Server 2016, 2019, 2022, 2025 | |
| Linux® x86-64 64-bit (linux64) | Red Hat® Enterprise Linux 8, 9, 10 | |
| SUSE® Enterprise Linux 15, 16 | ||
| Ubuntu® 22.04, 24.04, 26.04 | ||
| Amazon Linux 2, 2023 | ||
| Mac OS 64-bit (macos_universal2) | 15 (Sequoia), 26 (Tahoe) | |
| Linux® arm64 64-bit (armlinux64) | Red Hat® Enterprise Linux 8, 9, 10 | |
| SUSE® Enterprise Linux 15, 16 | ||
| Ubuntu® 22.04, 24.04, 26.04 | ||
| Amazon Linux 2, 2023 |
Supported Browsers by the Cluster Manager Web UI Supported Browsers
| Browser | Minimum Version | Notes |
|---|---|---|
| Chrome | 87 | |
| Firefox | 87 | |
| Edge | 44 | |
| Safari | 14 |
Supported Databases by the Cluster Manager Supported Databases
| Database | Minimum Version | Notes |
|---|---|---|
| MongoDB | 7.0 and up | |
| Amazon DocumentDB | 5.0 and up | Support for 4.0 has been discontinued, see Removed Features. |
| Azure Cosmos DB | 7.0 and up | Support for versions below 7.0 has been discontinued, see Removed Features. |
Removed Features
- Support for Amazon DocumentDB versions below 5.0 has been discontinued. Amazon DocumentDB 4.0 reports MongoDB wire protocol version 7, while current MongoDB drivers require wire protocol version 8, which corresponds to MongoDB 4.2 or later. If your Cluster Manager uses a version of Amazon DocumentDB below 5.0, you must upgrade your cluster to Amazon DocumentDB 5.0 or later before upgrading the Cluster Manager. Amazon Web Services supports in-place major version upgrades from the AWS Management Console or the AWS CLI.
- Support for Azure Cosmos DB for MongoDB versions below 7.0 has been discontinued. If your Cluster Manager uses an older Azure Cosmos DB version, you must upgrade your cluster to version 7.0 or later before upgrading the Cluster Manager. See Microsoft's Azure Cosmos DB for MongoDB upgrade guide for instructions.
New or Improved Features
Global Updates
- Gurobi Compute Server now supports Gurobi Optimizer 14.0.x, in addition to past releases 12.0.x and 13.0.x. Support for Gurobi Optimizer 11.0.x has been discontinued; it is no longer supported nor packaged in the compute server.
- The reference manual of the Gurobi remote services, including the Compute Server and the Cluster Manager, is available on the online documentation website.
Cluster Manager
- The Cluster Manager Web UI has been rewritten in TypeScript. This brings stronger type safety across the frontend codebase, catching a broad class of errors at build time rather than at runtime, and sets up the UI for faster, safer feature development going forward. The rewrite preserves existing functionality and does not require any action from users.
- The interactive API reference in the Cluster Manager Web UI, previously rendered with Swagger UI, now uses Scalar. This provides a more modern and easier-to-use interface for browsing and trying out the REST API, and reduces the size of the Web UI bundle. The API itself is unchanged and no action is required from users.
- The Cluster Manager now decides if a Compute Server node is alive based only on its own clock. Previously, a node whose clock was more than one minute behind the Cluster Manager's was removed from the cluster at every keepalive. Now, a difference between clocks no longer affects whether a node is considered alive: a node is removed only after
DISCONNECT_TIMEOUTwithout keepalive. Clock differences above 10 seconds are logged and shown in a newSKEWcolumn ofgrbcluster nodes. - New
DISCONNECT_TIMEOUT(default 60) andREGISTRY_REFRESH_INTERVAL(default 20) properties, in seconds, ingrb_rsm.cnf.
Database
No major updates. Note that support for Amazon DocumentDB versions below 5.0 and Azure Cosmos DB versions below 7.0 has been discontinued, see Removed Features.
Compute Server
Fixed a network deadlock that could occur on the Compute Server's internal command channel between the server and its workers while a solve is running. If a response to a worker command was lost in transit, the server had no safe way to retry the request without risking the worker re-executing the command or the connection stalling. The channel now uses a call-index based idempotent retry protocol, active only for the duration of a solve: each request carries a monotonically increasing call index, and repeating a request with the same index replays the previously stored response instead of re-issuing the command to the worker. This resolves the deadlock and is most noticeable in clusters running large numbers of small, short-running jobs.
License Agreement
Note that this software is covered by the Gurobi End User License Agreement. By completing the Gurobi installation process and using the software, you are accepting the terms of this agreement.
Thank you for using Gurobi products!
© 2026 Gurobi Optimization. All Rights Reserved.