diff --git a/docs/software_ready/ADRs/harbor_as_image_registry.md b/docs/software_ready/ADRs/harbor_as_image_registry.md
new file mode 100644
index 0000000..c447081
--- /dev/null
+++ b/docs/software_ready/ADRs/harbor_as_image_registry.md
@@ -0,0 +1,42 @@
+---
+title: "Harbor as Image Registry"
+date: "2025-03-31"
+---
+
+| status: | date: | decision-makers: |
+| --- | --- | --- |
+| proposed | 2025-03-31 | Kasper Møller |
+
+## Context and Problem Statement
+
+Containerized applications require a reliable and secure image registry to store and distribute container images. The chosen solution must integrate seamlessly with Kubernetes, provide robust security features, and support scalability for future growth.
+
+The question is: **Which container image registry should we use for our on-premises Kubernetes cluster?**
+
+## Considered Options
+
+* **Harbor:** An open-source, cloud-native registry that provides vulnerability scanning, role-based access control (RBAC), and image replication. It integrates well with Kubernetes and supports OCI-compliant images.
+* **JFrog Artifactory:** A universal artifact repository manager that supports container images, binaries, and other artifacts. It offers advanced features like high availability, replication, and enterprise-grade security but comes with licensing costs.
+* **Sonatype Nexus:** A repository manager that supports container images and other artifacts. It provides features like vulnerability scanning and integration with CI/CD pipelines. Has almost feature parity with Artifactory, and also comes with licensing costs.
+
+## Decision Outcome
+
+Chosen option: **Harbor**, because it provides a strong balance of features, open-source flexibility, and seamless integration with Kubernetes, while avoiding the licensing costs associated with commercial solutions.
+
+### Consequences
+
+* **Good, because:**
+  * Harbor is open-source and free to use, reducing costs.
+  * It provides robust security features, including vulnerability scanning and RBAC, which align with our security requirements.
+  * It integrates well with Kubernetes and supports image replication, making it suitable for multi-cluster setups.
+  * Harbor supports Helm charts and OCI-compliant libraries, making it versatile for managing not only container images but also other Kubernetes-related artifacts.
+
+* **Bad, because:**
+  * Harbor's user interface and feature set may not be as polished or extensive as JFrog Artifactory. User/role section is no way as feature rich and extensible as the competitors, only providing a fixed set of roles with limits in how much you can change.
+  * It lacks some advanced enterprise features, such as those offered by Artifactory, which might be needed for highly complex environments.
+  * It only supports OCI and helm repositories as its types of artifacts. If you need more than that, then choose one of JFrog Artifactory or Sonatype Nexus.
+
+### Recommendations
+
+* For organizations that require a cost-effective, Kubernetes-native solution with strong security features and support for Helm charts and OCI-compliant libraries, Harbor is an excellent choice.
+* For teams with complex artifact management needs and a budget for licensing, JFrog Artifactory may be a better fit due to its advanced features and broader artifact support.
diff --git a/docs/software_ready/_index.md b/docs/software_ready/_index.md
index 5a84950..23e3bb0 100644
--- a/docs/software_ready/_index.md
+++ b/docs/software_ready/_index.md
@@ -6,7 +6,7 @@ title: Getting your software ready
 
 | Problem domain | Description | Reason for importance | Tool recommendation |
 |:---:|:---:|:---:|:---:|
-| Image Registry | A common place to store and fetch images | High availability, secure access control | |
+| Image Registry | A common place to store and fetch images | High availability, secure access control | [Harbor](ADRs/harbor_as_image_registry.md) |
 | Secret Management | Securely store and manage sensitive information like passwords and API keys | Prevent unauthorized access and data leaks | |
 | Ingress Controller / Gateway API | Manage external access to services in the cluster | Enable routing, load balancing, and secure communication | |
 | GitOps / Deployment Pipelines | Automate application deployments using Git as the source of truth | Ensure consistency, traceability, and faster deployments | |