Lightbridge is a "Build in Public" project to replace legacy, monolithic VNAs with a modern, scalable, and cost-effective architecture.
It is a cloud-native Vendor Neutral Archive (VNA) built on Kubernetes. The project deploys an enterprise-grade DICOM engine (Orthanc) and Object Storage abstraction (MinIO) to AWS in minutes via Terraform.
📖 Read the full architecture series on Medium (Add your link here)
- Engine: Orthanc (DICOMweb/REST)
- Storage: MinIO (S3/Blob Abstraction) with KES Encryption
- Database: PostgreSQL (CloudNativePG Operator)
- Infrastructure: Terraform & Kubernetes (EKS/AKS)
- Security: Keycloak (OIDC), Cert-Manager (TLS 1.3), Linkerd (mTLS)
Before deploying Lightbridge, ensure you have the following installed:
-
Clone the repository
git clone [https://github.com/yourusername/lightbridge.git](https://github.com/yourusername/lightbridge.git) cd lightbridge -
Initialize Infrastructure
cd terraform terraform init terraform apply -
Deploy the Helm Chart
# Update dependency lock files helm dependency build charts/lightbridge # Install the stack helm install lightbridge charts/lightbridge -n medical-imaging --create-namespace
You are free to use, modify, and distribute this software for personal or commercial purposes. This license covers the Terraform code, Helm charts, documentation, and custom integration logic found in this repository.
Lightbridge VNA is released under the Apache License 2.0.
This project orchestrates several third-party open-source applications. While the automation code here is Apache 2.0, the applications themselves are subject to their own licenses:
| Component | License | Note |
|---|---|---|
| Orthanc | GPLv3 | Strong copyleft (General Public License) |
| MinIO | AGPLv3 | Network-protective copyleft (Affero General Public License) |
| PostgreSQL | PostgreSQL | Permissive License |
⚠️ Note for Commercial Users: If you plan to offer this stack as a commercial SaaS product, please review the AGPLv3 implications regarding MinIO and the GPLv3 implications regarding Orthanc. Lightbridge interacts with these services via standard APIs (HTTP/REST/DICOM), which generally maintains separation, but you are responsible for ensuring your deployment complies with their respective terms.
This software is for educational and research purposes only. It is not FDA-cleared or CE-marked for clinical diagnosis or treatment.