Oregon State University Open Source Lab

United States · osuosl.org · 6 vendors

The Oregon State University Open Source Lab (OSUOSL) is a nonprofit organization that provides hosting, software development, and training to advance open source technologies. It supports over 150 high-impact open source projects globally, including those from the Apache Software Foundation, the Linux Foundation, and Drupal, delivering hundreds of terabytes of information monthly.

Resilience scores

Disruption prediction

Oregon State University Open Source Lab has an estimated 27% probability of disruption in the next 6 months.

5 of Oregon State University Open Source Lab's 6 vendors monitored for disruptions.

Technology vendors

Services catalogue

5 services in catalogue across 3 categories; runs on 6 sub-vendors.

Insights

Last updated 2026-07-30 · revision 1

6 direct vendors, 122 subvendors

Direct vendors by controlling owner country (sample)

Subvendors by controlling owner country (sample)

Migration Readiness: 5/10

Assessed by AI based on technology stack characteristics (cloud-native vs legacy, containerization, microservices), regulatory environment, data residency requirements, financial stability, and vendor lock-in risks. The score ranges from 0-10, where higher scores indicate better readiness for technology migration.

OSUOSL exhibits medium migration readiness. The internal tech stack is a significant strength, featuring OpenStack (indicating private cloud experience), KVM virtualization, Docker for containerization, and robust CI/CD pipelines (Jenkins, GitLab CI/CD). These technologies align well with cloud-native principles and demonstrate a strong technical foundation for adopting public cloud services. Furthermore, the absence of specified data residency requirements provides flexibility in choosing cloud deployment locations. However, a major challenge to migration readiness stems from the core business model: providing specialized hosting on specific hardware architectures (AARCH64, IBM POWER, IBM Z) through partnerships with Ampere Computing, IBM, and Marist College. Migrating these highly specialized, bare-metal or specific-architecture virtualized workloads to generic public cloud environments would be complex, likely requiring significant re-architecture or reliance on niche cloud offerings that support these specific architectures. This deep integration with specialized hardware and partners creates a form of architectural vendor lock-in. While "Total Vendors: 0" is stated, if the partnerships are considered vendors (Ampere, IBM, Marist College), their limited number (3) and geographic concentration (United States) indicate a moderate lock-in risk for these specialized services. Crucial data regarding financial stability (ability to fund migration) and the regulatory environment (compliance requirements) is missing, which are vital factors for a complete migration readiness assessment.

Signed-in users can see whether their own company is exposed to this vendor's disruption, plus the full sub-vendor list and country breakdowns, every in-scope compliance framework plus gaps and next steps, and alerts when any of it changes.

View the full interactive report