Skip to main content

The Secrets to Success with Open Source

Rod Cope
Perforce Software

In the age of digital transformation, enterprises are migrating to open source software (OSS) in droves to streamline operations and improve customer and employee experiences. However, to unlock the deluge of OSS benefits, it's not enough for organizations to simply implement the software. They must take the necessary steps to build an intentional OSS strategy rooted in ongoing third-party support and training.

To better understand the current state of OSS and how enterprises' varying levels of support and training efforts correlated with business success, we worked with Forrester Consulting to survey leading open source and cloud adoption decisionmakers at North American enterprises and uncovered an overarching theme: when running open source packages, companies need third-party expertise and skilled resources to fully realize their business goals.

Non-Optimized Support and Lifecycle Management Limit OSS Success

Open source software has emerged as a central pillar of enterprises' efforts to future-proof their IT strategies. When implemented correctly, it delivers tremendous business value, from greater flexibility and innovation to reduced costs and security threats. In fact, an overwhelming 96% of enterprises find OSS mission critical or important to their company's digital transformation initiatives and 97% intend to move at least one aspect of their IT infrastructure to OSS, according to the Forrester study.

Despite this welcome attitude toward open source software adoption, few have taken the necessary steps to embrace it fully, and run it at enterprise scale, securely, with minimized risk and maximized results. The idea of OSS is appealing, but when it comes time to implement, enterprises often don't understand how the individual technologies operate or how to take advantage of OSS in a comprehensive manner. Rather than establishing enterprise-wide policies for overseeing and regulating their open source, they leave it to individual departments or developers to control.

The result? 64% of enterprises report sub-optimal, siloed approaches that fail to factor in the external expertise or skills required of sophisticated OSS. Consequently, these enterprises risk falling behind in maintenance lifecycles, losing out to their modernized competitors, increasing security vulnerabilities and struggling to hire and retain talent that prefer OSS environments.

Even though a majority of organizations reported subpar OSS strategies, they understood the value external skills and support could have on their success and were receptive to change. Areas respondents believe would benefit from greater assistance include initial setup and architecture design, ongoing maintenance of OSS implementations and improved access to training, among others.


Digital transformation requires more than the mere adoption of new technologies; it demands an ongoing, holistic approach. There are a host of OSS factors that, left unchecked, could result in disaster for businesses and their bottom line.

External OSS Guidance Leads to Better Business Outcomes

In the Forrester report, nearly every respondent who adopted open source experienced at least one of its benefits, including greater flexibility, faster product innovation, enhanced employee experiences, lower operational overhead and better customer satisfaction. However, those who added ongoing external support services to their open source strategy were 82% more likely to report that they exceeded business expectations, underscoring the tremendous cost-benefit of third-party support.


Despite these findings, many organizations have not optimized their OSS strategies with enterprise-level support and maintenance — effectively missing out on such benefits as greater flexibility, efficiency and innovation.

For those enterprises that are eager to close this gap, but are unsure of where to start, consider conducting an internal audit of the key areas required of a robust OSS strategy: security, support and maintenance.

Businesses should ask themselves the following questions to help pinpoint their current position:

■ Are the business-critical components you are using supported commercially?

■ Do you oversee or monitor the OSS packages teams are allowed to deploy?

■ How often do you experience expensive service interruptions or outages?

■ Do you find that architectural changes are necessary to resolve production issues?

■ How much time do your developers spend engaging in support roles?

If IT and DevOps teams are spending most of their time fixing bugs, self-supporting or rearchitecting applications, it may be time to tap a third-party support group to manage the many moving parts associated with a fully-realized open source strategy. Not only will added support and skills better position enterprises for long-term IT excellence, but it'll quickly catapult them into the elite 82% of organizations outpacing their business goals.

Rod Cope is CTO of Perforce Software

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...

The Secrets to Success with Open Source

Rod Cope
Perforce Software

In the age of digital transformation, enterprises are migrating to open source software (OSS) in droves to streamline operations and improve customer and employee experiences. However, to unlock the deluge of OSS benefits, it's not enough for organizations to simply implement the software. They must take the necessary steps to build an intentional OSS strategy rooted in ongoing third-party support and training.

To better understand the current state of OSS and how enterprises' varying levels of support and training efforts correlated with business success, we worked with Forrester Consulting to survey leading open source and cloud adoption decisionmakers at North American enterprises and uncovered an overarching theme: when running open source packages, companies need third-party expertise and skilled resources to fully realize their business goals.

Non-Optimized Support and Lifecycle Management Limit OSS Success

Open source software has emerged as a central pillar of enterprises' efforts to future-proof their IT strategies. When implemented correctly, it delivers tremendous business value, from greater flexibility and innovation to reduced costs and security threats. In fact, an overwhelming 96% of enterprises find OSS mission critical or important to their company's digital transformation initiatives and 97% intend to move at least one aspect of their IT infrastructure to OSS, according to the Forrester study.

Despite this welcome attitude toward open source software adoption, few have taken the necessary steps to embrace it fully, and run it at enterprise scale, securely, with minimized risk and maximized results. The idea of OSS is appealing, but when it comes time to implement, enterprises often don't understand how the individual technologies operate or how to take advantage of OSS in a comprehensive manner. Rather than establishing enterprise-wide policies for overseeing and regulating their open source, they leave it to individual departments or developers to control.

The result? 64% of enterprises report sub-optimal, siloed approaches that fail to factor in the external expertise or skills required of sophisticated OSS. Consequently, these enterprises risk falling behind in maintenance lifecycles, losing out to their modernized competitors, increasing security vulnerabilities and struggling to hire and retain talent that prefer OSS environments.

Even though a majority of organizations reported subpar OSS strategies, they understood the value external skills and support could have on their success and were receptive to change. Areas respondents believe would benefit from greater assistance include initial setup and architecture design, ongoing maintenance of OSS implementations and improved access to training, among others.


Digital transformation requires more than the mere adoption of new technologies; it demands an ongoing, holistic approach. There are a host of OSS factors that, left unchecked, could result in disaster for businesses and their bottom line.

External OSS Guidance Leads to Better Business Outcomes

In the Forrester report, nearly every respondent who adopted open source experienced at least one of its benefits, including greater flexibility, faster product innovation, enhanced employee experiences, lower operational overhead and better customer satisfaction. However, those who added ongoing external support services to their open source strategy were 82% more likely to report that they exceeded business expectations, underscoring the tremendous cost-benefit of third-party support.


Despite these findings, many organizations have not optimized their OSS strategies with enterprise-level support and maintenance — effectively missing out on such benefits as greater flexibility, efficiency and innovation.

For those enterprises that are eager to close this gap, but are unsure of where to start, consider conducting an internal audit of the key areas required of a robust OSS strategy: security, support and maintenance.

Businesses should ask themselves the following questions to help pinpoint their current position:

■ Are the business-critical components you are using supported commercially?

■ Do you oversee or monitor the OSS packages teams are allowed to deploy?

■ How often do you experience expensive service interruptions or outages?

■ Do you find that architectural changes are necessary to resolve production issues?

■ How much time do your developers spend engaging in support roles?

If IT and DevOps teams are spending most of their time fixing bugs, self-supporting or rearchitecting applications, it may be time to tap a third-party support group to manage the many moving parts associated with a fully-realized open source strategy. Not only will added support and skills better position enterprises for long-term IT excellence, but it'll quickly catapult them into the elite 82% of organizations outpacing their business goals.

Rod Cope is CTO of Perforce Software

The Latest

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Many organizations assumed their infrastructure strategy was settled. It had been implemented, optimized and built into long-term plans. Recent changes in technology and vendor consolidation are forcing a second look. Cloud outages and licensing changes have exposed how much dependency exists on a small number of platforms. As a result, organizations are reevaluating whether those decisions still hold up under current conditions ...

Edge AI is strategically embedded in core IT and infrastructure spending across industries, according to the 2026 Edge AI Survey from ZEDEDA. The research shows that 83% of C-suite and IT executive respondents say edge AI is important to their core business strategy ...

As AI adoption accelerates, operational complexity — not model intelligence — is becoming the primary barrier to reliable AI at scale, according to the State of AI Engineering 2026 from Datadog ... The report highlights a compounding complexity challenge as AI systems scale ... Around 5% of AI model requests fail in production, with nearly 60% of those failures caused by capacity limits ...

For years, production operations teams have treated alert fatigue as a quality-of-life problem: something that makes on-call rotations miserable but isn't considered a direct contributor to outages. That framing doesn't capture how these systems fail, and we now have data to show why. More importantly, it's now clear alert fatigue is a symptom of a deeper issue: production systems have outgrown the current operational approaches ...

I was on a customer call last fall when an enterprise architect said something I haven't been able to shake. Her team had just spent four months trying to swap one AI vendor for another. The original plan said three weeks. "We didn't switch vendors," she told me. "We rebuilt half our integrations and discovered what we'd actually been depending on." Most enterprise leaders don't expect that to be the experience ...

Ask any senior SRE or platform engineer what keeps them up at night, and the answer probably isn't the monitoring tool — it's the data feeding it. The proliferation of APM, observability, and AIOps platforms has created a telemetry sprawl problem that most teams manage reactively rather than architect proactively. Metrics are going to one platform. Traces routed somewhere else. Logs duplicated across multiple backends because nobody wants to be caught without them when something breaks. Every redundant stream costs money ...

80% of respondents agree that the IT role is shifting from operators to orchestrators, according to the 2026 IT Trends Report: The Human Side of Autonomous IT from SolarWinds ...