GitLab Server
Discover the features, configurations and best practices for using your GitLab instance.
Available instance layouts
| GitLab Professional | GitLab Business | GitLab Enterprise |
|---|---|---|
| Recommended for 50 users | Recommended for 200 users | Recommended for 500 users |
| 4 vCPUs | 6 vCPUs | 8 vCPUs |
| 10 GB RAM | 16 GB RAM | 32 GB RAM |
| 50 GB SSD OS 50 GB SSD data | 50 GB SSD OS 200 GB SSD data | 50 GB SSD OS 450 GB SSD data |
| Veeam B&R backups | Veeam B&R backups | Veeam B&R backups |
| Email support | Email support | Email support |
Also, you can view the available GitLab Runner layouts.
Available options
- Data import from an existing GitLab
- Authentication: SSO, AD, OmniAuth
- GitLab Pages
- Advanced Search
- Kroki
- Personal certificates
- Disk encryption
- Additional disk space
- VPN / IP filtering
- Additional bandwidth
- Export GitLab data backup to the storage medium of your choice
- Outsourcing of application logs at your premises
Applying GitLab update
At adista, we carry out two types of updates:
- Monthly updates
- Security updates
Monthly updates
To ensure the stability and the security of your GitLab instance, we follow a monthly update policy.
Updates are applied on the 4th Thursday of each month, from 9.30 pm (CEST).
GitLab releases a new minor version on the 3rd Thursday of every month. As soon as it is available, our team installs it internally, and it undergoes a series of tests for a week. This period also allows us to integrate any fixes released by GitLab in the meantime.
At the end of this validation phase, the minor version, along with any bug fixes released in the meantime, are deployed to your platform during the monthly maintenance window. This approach aims to minimize the risks associated with introducing new features or unforeseen regressions.
Upcoming GitLab Releases
| Version | Release date | Deployment date by adista |
|---|---|---|
| 19.4 | September 17, 2026 | September 24, 2026 |
| 19.5 | October 15, 2026 | October 22, 2026 |
| 19.6 | November 19, 2026 | November 26, 2026 |
| 19.7 | December 17, 2026 | December 28, 2026 (because of the end-of-year holidays) |
| 19.8 | January 21, 2027 | January 28, 2027 |
| 19.9 | February 18, 2027 | February 25, 2027 |
| 19.10 | March 18, 2027 | March 25, 2027 |
| 19.11 | April 15, 2027 | April 22, 2027 |
| 20.0 | May 20, 2027 | May 27, 2027 No version upgrade, but an update to the latest 19.11 |
| 20.1 | June 17, 2027 | June 24, 2027 |
| 20.2 | July 15, 2027 | July 22, 2027 |
| 20.3 | August 19, 2027 | August 26, 2027 |
Specific features of major version deployment
GitLab releases a new major version every year, in May. These versions add significant changes and deprecations, as well as potential bugs.
As a precaution, we do not deploy this version immediately, but rather wait until the following month, when the next patch release (containing initial bug fixes) is released, before proceeding with the installation.
GitLab provides support for the three most recent minor versions: N, N-1 and N-2. Therefore, delaying the installation of a major version by one month has no impact on the security of your instance. Security patches will continue to be released for version N-1, which is then installed on your instance, thus ensuring that your environment remains secure.
Security updates
There is no need to open a ticket when GitLab notifies you that an update is available. Our team is already informed of the patch release and is handling its analysis, and will deploy it according to established procedures.
When a security patch is released, a pop-up message appears on your GitLab interface, prompting you to update as soon as possible. We are already aware of this patch, and we are conducting a thorough analysis of its potential impact on your infrastructure.
If our team determines that your system is affected by a critical vulnerability, you will be notified immediately. In this case, we will schedule an exceptional update as soon as possible.
However, if we determine that your system is not affected, our team will not contact you unnecessarily, and your GitLab instance will be updated at the end of the month, as part of our regular monthly maintenance schedule. This approach aims to ensure optimal security for your platform.
If you have any questions about your subscription or the GitLab solution offered by adista, please contact your dedicated sales representative, who will be happy to assist you.
Review the release notes
To stay up to date with GitLab's developments and learn about the details of new releases, you can consult the official release notes.
Anticipate breaking changes
Some updates may introduce major changes and deprecations. To anticipate these changes and adapt your workflows accordingly, we recommend that you regularly review the dedicated documentation.