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 vCPU |
| 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
Information on 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 an monthly update policy.
Updates are applied on the 4th Tuesday of each month, from 9.30 pm (CEST).
GitLab releases a new minor version on the third Tuesday 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 this introducing new features or unforeseen regressions.
Upcoming GitLab Releases
| Version | Date de publication | Date de déploiement par adista |
|---|---|---|
| 18.4 | 19 septembre 2025 | 25 septembre 2025 |
| 18.5 | 16 octobre 2025 | 23 obtobre 2025 |
| 18.6 | 20 novembre 2025 | 27 novembre 2025 |
| 18.7 | 18 décembre 2025 | 5 janvier 2026 (car fêtes de fin d'année) |
| 18.8 | 15 janvier 2026 | 22 janvier 2026 |
| 18.9 | 19 février 2026 | 26 février 2026 |
| 18.10 | 19 mars 2026 | 26 mars 2026 |
| 18.11 | 16 avril 2026 | 23 avril 2026 |
| 19.0 | 21 mai 2026 | Pas de mise à jour, but update to last 18.11 |
| 19.1 | 18 juin 2026 | 25 juin 2026 |
| 19.2 | 16 juillet 2026 | 23 juillet 2026 |
| 19.3 | 20 aout 2026 | 27 aout 2026 |
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 thress 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-!, 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. Out tems are already informed of the patch release and are 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 the availability of the patch's availability, 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, out team will not contact your 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 uour dedicated sales representative, who will be happy to assis you.
Review the release notes
To stay up to date with GitLab's developments adn 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 recommand that you regurlarly review the dedicated documentation.