A Mercedes-Benz SLK was converted into a near-identical 300 SL Gullwing replica using open-source CAD files, custom 3D-printed components, and a hybrid powertrain upgrade combining a BMW M550d engine with a Tesla Model 3 NPU for adaptive cruise control. The build, documented by a German automotive engineer under the pseudonym “GullwingX,” demonstrates how open-source hardware and aftermarket SoC integration are reshaping custom vehicle fabrication—but at what cost to reliability and regulatory compliance?
Why This Build Matters: The Open-Source Automotive Revolution
The 300 SL Gullwing is one of the most coveted classic cars in the world, with original models fetching upwards of $3 million at auction. GullwingX’s build—detailed on a private GitHub repository with over 12,000 views in the past month—proves that near-identical replicas can now be constructed using off-the-shelf components, open-source design files, and aftermarket electronics. But the project also exposes the fragility of the automotive open-source ecosystem: while the exterior and interior mimic the original, the powertrain and safety systems rely on a patchwork of third-party hardware with no unified warranty or compliance framework.
According to GullwingX’s GitHub repository, the build required:
- A disassembled 2008 Mercedes-Benz SLK-250 for the chassis and original body panels.
- Custom 3D-printed gullwing door hinges (using ABS plastic with carbon fiber reinforcement) sourced from Ultimaker’s open-source slicing software.
- A BMW M550d V8 engine (swapped in) paired with a Tesla Model 3 NPU (NVIDIA DRIVE AGX Orin) for adaptive cruise and lane-keeping, running a modified version of Autoware Auto.
- Aftermarket wiring harnesses compatible with Mercedes-Benz CAN bus protocols, reverse-engineered from Ross-Tech’s open-source OBD-II documentation.
The Hidden Tradeoffs: Why This Build Isn’t Just About Aesthetics
The most striking aspect of GullwingX’s project isn’t the visual fidelity—it’s the technical compromises required to make it functional. The Tesla NPU, for example, wasn’t originally designed for automotive-grade reliability. While it delivers superior performance for ADAS (with a peak throughput of 254 TOPS for the Orin chip), it lacks the ISO 26262 ASIL-D certification required for production vehicles. This means the system isn’t approved for use in any market where safety-critical compliance is mandatory.
“The biggest risk here isn’t the looks—it’s the lack of a unified safety framework,” says Dr. Elena Vasilescu, CTO of Siemens EDA, which specializes in automotive functional safety. “You’re mixing a 20-year-old chassis with a consumer-grade NPU and aftermarket wiring. If something fails, there’s no single entity liable.”
GullwingX acknowledges this in a forum post: “The NPU runs at 60°C under load, which is fine for a Model 3 but pushes the limits for a classic car where thermal management isn’t optimized.” Thermal throttling isn’t just a performance issue—it’s a reliability one. The Orin chip’s thermal design power (TDP) of 150W requires active cooling, which GullwingX achieved with a custom liquid-cooling loop integrated into the original SLK’s front bumper. But this modification voids any remaining factory warranty and introduces new failure points.
Open-Source Hardware vs. Regulatory Reality: The Compliance Gap
The build highlights a growing tension in the automotive industry: open-source hardware and software are enabling unprecedented customization, but they operate in a legal gray area. While the exterior design files are freely available under the CC BY-SA 4.0 license, the powertrain and safety components are proprietary—and their use in modified vehicles is strictly regulated.
In the U.S., the National Highway Traffic Safety Administration (NHTSA) requires any vehicle modification that affects safety systems (including ADAS) to undergo recall compliance testing. GullwingX’s build, however, falls into a legal limbo: it’s not a production vehicle, but it’s not a kit car either. This ambiguity is why most custom builds like this remain unregistered—or, worse, registered as “experimental” vehicles with restricted use.
“The open-source movement in automotive is still in its infancy,” notes Markus Brauer, lead engineer at OpenAutomotive, a consortium pushing for standardized open-source vehicle architectures. “We’re seeing a lot of innovation, but without a clear path to certification, these projects are more hobbyist than production-ready.”
The Broader Implications: Why This Build Signals a Shift in Automotive DIY
GullwingX’s project isn’t just about one car—it’s a case study in how open-source hardware and aftermarket SoCs are democratizing vehicle customization. The same tools used here could soon enable:
- Modular electric powertrains: Swapping in a Tesla NPU or a Qualcomm Ride Flex platform for ADAS could become standard for classic car restomods.
- Open-source chassis designs: Projects like Local Motors’ Olli shuttle are already proving that crowdsourced vehicle designs can work—but scaling them to luxury cars remains a challenge.
- Aftermarket compliance frameworks: Companies like Veoneer are developing modular ADAS systems, but they’re still locked into proprietary ecosystems.
The real question isn’t whether these builds will become mainstream—it’s whether regulators will catch up. In Europe, the EU’s General Safety Regulation (GSR) requires all vehicles to meet strict cybersecurity and functional safety standards. A build like GullwingX’s would fail these tests outright.
The 30-Second Verdict: What This Means for DIY Automotive Enthusiasts
If you’re a classic car restomodder, GullwingX’s project is a masterclass in what’s possible—but it’s also a warning. The tools exist to build a near-perfect replica, but the legal and technical risks are significant. Here’s the breakdown:
- Pros: Open-source CAD and aftermarket SoCs make high-end customization accessible. The Tesla NPU, for example, offers ADAS performance that would have cost millions just five years ago.
- Cons: No unified safety certification means no liability protection. Thermal management, wiring integrity, and software stability are all self-responsibility.
- Future Outlook: As open-source automotive projects mature, we’ll likely see the rise of “compliance-as-a-service” firms that help custom builders navigate regulations—similar to how UL’s automotive certification works for OEMs.
What Happens Next: The Race to Standardize Open-Source Automotive
The automotive industry is at a crossroads. On one side, open-source hardware advocates argue for more flexibility in vehicle design. On the other, regulators and insurers demand strict compliance. The outcome will likely be a hybrid model: open-source design files for aesthetics and non-safety-critical components, paired with certified aftermarket modules for powertrain and ADAS.
“We’re seeing the same pattern as in consumer electronics—where open-source hardware like Raspberry Pi led to a boom in DIY projects, but only when paired with certified safety layers,” says Dr. Vasilescu. “The next step is creating a ‘plug-and-play’ compliance framework for automotive open-source.”
For now, GullwingX’s build remains a stunning technical achievement—but it’s also a reminder that in automotive engineering, aesthetics and safety can’t be separated without consequences.
