diff --git a/README.md b/README.md
index b0619ab45..1c7d04369 100644
--- a/README.md
+++ b/README.md
@@ -76,3 +76,32 @@ singularity  mulled-v2-eb9e7907c7a753917c1e4d7a64384c047429618a  e4be5f66213daef
  - Create quay.io oauth token in an organization.
  - Change the [MULLED_NAMESPACE variable](https://github.com/BioContainers/multi-package-containers/blob/master/.github/workflows/ci.yaml#L4) to point to your quay.io organization.
  - Add QUAY_OAUTH_TOKEN, MY_USER MY_PASSWORD and MY_EMAIL to the repository secrets.
+
+
+## Broader context
+
+[Bioconda](https://bioconda.github.io/) and [Conda-Forge](https://conda-forge.org/) are collaborative communities focused on creating and maintaining Conda recipes.
+These recipes facilitate the installation and management of scientific software,
+providing researchers and developers with streamlined workflows. Packages from both [Bioconda](https://bioconda.github.io/) and [Conda-Forge](https://conda-forge.org/)
+are hosted on [anaconda.org](https://anaconda.org/), a central repository that ensures reliable distribution.
+
+The process for managing these packages is highly automated. Both Bioconda and Conda-Forge build and upload pre-compiled packages directly to anaconda.org. Bioconda goes a step further by testing all packages in minimal containerized environments to verify their compatibility and reliability. These containerized versions of the packages are subsequently pushed to quay.io/biocontainers, creating a robust and accessible ecosystem of ready-to-use environments.
+
+For every package and every version within Bioconda, a corresponding pre-built container is available. This approach ensures that users have access to specific versions of tools in isolated and consistent environments.
+Additionally, the multi-package-containers repository builds containers that include multiple Conda packages in a single container, known as mulled containers.
+The naming convention for these containers relies on hashed package names and versions, providing unique identifiers for each.
+Docker containers are directly pushed to quay.io/biocontainers, while Singularity images are uploaded to depot.galaxyproject.org/singularity.
+
+To ensure seamless synchronization between these platforms, the [singularity-build-bot](https://github.com/BioContainers/singularity-build-bot) repository monitors quay.io for updates and uploads the corresponding containers
+to [depot.galaxyproject.org](https://depot.galaxyproject.org/singularity/).
+This ensures that all containers available on quay.io are also accessible via [depot.galaxyproject.org/singularity](https://depot.galaxyproject.org/singularity/).
+
+Singularity containers hosted on depot.galaxyproject.org are further mirrored and geographically distributed using the CernVM File System (CVMFS).
+This infrastructure optimizes access to containers globally, providing end-users with a reliable and efficient way to consume these resources.
+The CVMFS distribution model parallels the accessibility of [quay.io/biocontainers](https://quay.io/organization/biocontainers), ensuring that users can seamlessly integrate these resources into their workflows.
+
+![grafik](https://github.com/user-attachments/assets/d784c33f-aa92-47fa-a8fb-564f0cf69035)
+
+
+
+