A Path Forward After Cetitec

When Your Networking Vendor Closes Mid-Program

The closure of a technology vendor in the middle of an active program is one of the most disruptive events an automotive supplier or OEM can face. When Cetitec GmbH—the Porsche AG subsidiary known for network protocol stacks and tools—announced its closure on May 8, 2026 as part of a strategic realignment, it left capable engineering teams facing a difficult situation through no fault of their own. The teams who built integrations around the Cetitec platform did serious work. The problem is that the vendor no longer exists, and good engineers are left with a straightforward question that deserves a straightforward answer: what do we do now?

That question is exactly what our new migration guide, "Moving Beyond Cetitec," is designed to address. The guide focuses on practical clarity—helping affected teams understand precisely what they need to replace, what maps cleanly to an alternative, and how to make the transition with minimal program impact. It's written for the people in the thick of it, whether they're early in development or deep into validation and production.

The guide walks through the full picture in concrete terms. It starts by helping teams map their actual Cetitec dependencies—from the Universal Gateway signal-routing library and the CMS middleware framework to the CETIBOX H3 hardware and the Composer/Integra toolchain—so they can gauge their real exposure by program phase. From there, it lays out Excelfore in-vehicle networking stacks that form a strong path forward, covering the full IEEE 802.1 AVB/TSN traffic management suite, AVTP support, and a production-deployed diagnostics and middleware suite spanning SOVD, UDS, DoIP, SOME/IP, and more.

Most usefully, it offers a practical five-step transition sequence:

1. 1. 1. 1.    1. Assess the dependency map,
         2.    2. Replace the hardware first (the Excelfore Mini Test Tool is the most direct CETIBOX H3 replacement),
         3.    3. Map gateway configuration to YANG/NetConf,
         4.    4. Migrate middleware and diagnostics, and
         5.    5. Plan AVNU certification directly through Excelfore.

If your program has been affected by the Cetitec closure, the guide is the clearest place to start understanding your options. There's no single migration timeline that fits every team—and the goal here is clarity, not pressure.

Read the full guide: Moving Beyond Cetitec — available on the Excelfore downloads page