**The selection process for the initial Helmholtz Cloud service portfolio has been successfully completed.**
At the end of this process, 38 services offered by nine Helmholtz Centers were selected. Considering that some services are provided by several centers, the initial service portfolio includes 21 different services.
<!--more-->
# The Initial Service Portfolio:
In summary, the following services form the initial service portfolio of the Helmholtz Cloud:
**AWI Marketplace**, AWI
**B2Share (Invenio)**, Jülich
**Docker**, DESY
**GitLab**, HZDR, KIT, Jülich, GEOMAR
**GPU Compute Service**, Jülich, HZDR
**HAICORE (HAICU, HIP)**, KIT, Jülich
**JupyterHub**, Jülich, DESY, DKFZ, HMGU
**JupyterHub Notebooks on HPC**, KIT
**LimeSurvey**, HMGU, DKFZ
**Mattermost**, HZDR
**Nextcloud (OnlyOffice)**, KIT, HZB, DESY
**Ocean and Climate Sensor Management**, AWI
**ODV**, AWI
**OpenStack**, Jülich, KIT, DKFZ
**Redmine**, HZDR, HMGU
**Rocket.Chat**, Jülich
**RODARE**, HZDR
**ShareLaTex**, HZDR
**Singularity**, KIT, Jülich
**Storage (HDF)**, Jülich, DESY
**Zammad**, HZDR
# Service integration of the initial service portfolio:
The points obtained in the service selection process determine the ranking for service integration. The ranking roughly reflects the time required by the service providers as necessary preparation time (service readiness) for the services. A short preparation time was weighted comparatively high in the initial service portfolio; this weighting will be adjusted in future service selections.
The next step is to establish a roadmap for the service integration. Our goal is to have the first services available on the Technical Platform (pilot version) by the end of the year.
# Further development of the service portfolio:
In parallel to the integration of the initial service portfolio, those services that have achieved a lower score in the service selection process will be reassessed. The reason for low scores was often that services require a time-consuming preparation before they can be offered in the Helmholtz Cloud. In some cases, not all necessary information about the services were available, or internal processes within the center delayed a short-term provision.
