Skip to content

Docs CSC now features an automatic Finnish translation. Click here for more information.

Warning!

Puhti and Mahti are being decommissioned in stages, and their storage areas will become fully unavailable from 15 October 2026. Clean up unnecessary files and move any data you need to keep by 31 August 2026. See the Roihu data migration guide for instructions on transferring your data to Roihu.

Puhti scratch is very full: keep only active data there and move or delete everything else. No new Puhti scratch quota will be granted.

What is Satama

Recommendations

Before using Satama, we recommend that you familiarise yourself with containers.

Satama is a cloud-native container image registry for CSC. It is based on Harbor. Harbor is an open source CNCF graduated project and provides a more secure and feature-rich alternative to Docker Hub.

Satama provides a secure and centralized location for users to push, pull, and manage container images within CSC’s infrastructure. While it offers functionality similar to Docker Hub, it includes additional enterprise features such as role-based access control (RBAC), vulnerability scanning, image signing, and detailed audit logging.

By using Satama, teams can organize images into projects, control who can access or modify them, and ensure that only verified and authorized images are deployed across cloud and HPC environments. Built-in security features such as vulnerability scanning and SBOM generation help users understand image contents and identify potential risks before deployment.

Satama simplifies image lifecycle management by enabling consistent versioning, structured organization, and controlled sharing of container images. This ensures reproducibility, reliability, and compliance across development, research, and production workloads.

When should I choose Satama

Satama can be a good choice in following scenarios:

  • Need full control over container images and cannot rely on public registries. This is important if your workloads, research tools, or internal applications should not be exposed or affected by external changes.
  • If reproducibility matters and deployments must run with the exact same environment months later.
  • when security is a concern, it allows vulnerability scanning, controlled access to images, and tracking of who uploaded or modified something.
  • When multiple projects and users are involved, it provides structured access control and better organization of images.