Over the years, Intel has established itself as a paragon of the open source community, but that could soon change under the x86 giant's new leadership.

Speaking to press and analysts at Intel's Tech Tour in Arizona last week, Kevork Kechichian, who now leads Intel's datacenter biz, believes it's time to rethink what Chipzilla contributes to the open source community.

"We have probably the largest footprint on open source out there from an infrastructure standpoint," he said during his opening keynote. "We need to find a balance where we use that as an advantage to Intel and not let everyone else take it and run with it."

[1]

In other words, the company needs to ensure that its competitors don't benefit more from Intel's open source contributions than it does.

[2]

[3]

Speaking with El Reg during a press event in Arizona last week, Kechichian emphasized that the company has no intention of abandoning the open source community.

"Our intention is never to leave open source," he said. "There are lots of people benefiting from the huge investment that Intel put in there."

[4]

"We're just going to figure out how we can get more out of that [Intel's open source contributions] versus everyone else using our investments," he added.

A spokesperson later added the following clarification: "Intel remains deeply committed to open source. We’re sharpening our focus on where and how we contribute — ensuring our efforts not only reinforce the communities we’ve supported for decades but also highlight the unique strengths of Intel."

Open source software has numerous advantages. Transparency means that anyone can inspect the codebase and, if bugs, optimizations, or security vulnerabilities are discovered, the community can take immediate action to report, enhance, or patch them.

[5]

This transparency also means that code initially optimized for a particular piece of hardware - Intel's Xeon platform, for example - can be adapted to work with hardware from rival chip vendors like AMD, Qualcomm, or others.

This community-driven, cross compatibility can help push adoption as customers don't need to worry about whether their apps or services will misbehave when moving between platforms.

At the same time, it means that, with a bit more effort, rival chipmakers can use Intel's contributions as a shortcut to developing their own highly optimized libraries, and this appears to be the crux of Kechichian's problem.

How Intel intends to prevent rivals from gaining an advantage from its software developments isn't entirely clear. However, the company could choose to keep some aspects of its code base closed.

Intel's OneMKL math kernel libraries are a prime example. While many of the higher level interfaces are open source, the low-level math libraries themselves are closed.

What's more, at least at one point, Intel implemented a check that would detect rival CPU platforms and force the libraries to run the most basic implementations even after AVX2 vector extensions had been implemented.

[6]X2 Elite is Qualcomm's latest attempt to bring Apple's M-series magic to the PC

[7]Intel and Nvidia sitting in a tree, NVLink-I-N-G

[8]Intel talent bleed continues as Xeon chip architect heads for the escape hatch

[9]Intel pitches Clearwater Forest as a consolidation play for all you hoarding ancient Xeons

It's possible that Intel may choose to extend these protections to other projects. This would, however, come at the risk of greater fragmentation, where the existing codebase is forked and the broader open source community gravitates around a vendor-agnostic implementation.

And that could end up happening anyway if Intel can't allocate the resources necessary to maintain its existing contributions. The past year has seen Intel shed tens of thousands of workers. The resulting brain drain is hard to ignore.

Late last week, FOSS-friendly pub Phoronix [10]reported that many of the Debian and Ubuntu packages required to harness the accelerators baked into the chipmaker's processors had been orphaned. Affected libraries included key libraries and frameworks required to harness popular features like Intel's QuickAssist and Data Streaming accelerators. Just about two months earlier, several Linux drivers [11]suffered the same fate as their maintainers were handed pink slips. ®

Get our [12]Tech Resources



[1] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2aOfcF08oc2Eu9cMkzDwQXwAAAA8&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0

[2] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aOfcF08oc2Eu9cMkzDwQXwAAAA8&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[3] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aOfcF08oc2Eu9cMkzDwQXwAAAA8&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44aOfcF08oc2Eu9cMkzDwQXwAAAA8&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0

[5] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/front&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33aOfcF08oc2Eu9cMkzDwQXwAAAA8&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0

[6] https://www.theregister.com/2025/09/25/qualcomm_details_x2_elite/

[7] https://www.theregister.com/2025/09/18/nvidia_intel_deal_nvlink/

[8] https://www.theregister.com/2025/09/11/intel_loses_chief_architect/

[9] https://www.theregister.com/2025/08/27/intel_clearwater_forest/

[10] https://www.phoronix.com/news/Intel-Debian-Packages-Orphaned

[11] https://www.phoronix.com/news/Intel-More-Orphans-Maintainers

[12] https://whitepapers.theregister.com/