newsonline24

As vehicles become increasingly software-driven, OEMs, and Tier 1 suppliers face growing complexity in their E/E architectures. Configuration data is often scattered across multiple formats, tools, and departments — making it difficult to keep architecture, implementation, and testing aligned. The result is slower development cycles, higher coordination effort, and increased risk of inconsistencies and errors.

FLYNC tackles this challenge by introducing a single, shared source of truth for vehicle network configuration — one that is easy to understand, easy to maintain and easy to integrate into existing development workflows.

By treating configuration data like code, FLYNC enables teams to:

• Reduce manual effort and duplication across architecture, development, and testing
• Improve consistency and traceability throughout the vehicle lifecycle
• Accelerate collaboration between internal teams and external suppliers
• Shorten time-to-market by minimizing rework and configuration mismatches

“Today’s SDV programs suffer from configuration silos that slow teams down and create unnecessary friction,” says Iago Alvarez, Lead Engineer at Technica Engineering. “FLYNC helps organizations regain control by making configuration transparent, reproducible and collaborative.”

Designed with modern automotive development in mind, FLYNC fits naturally into Gitbased and CI/CD-driven environments, allowing configuration changes to be reviewed, versioned, and reused just like code. This approach helps to bridge the gap between system architecture, implementation, and validation, while remaining flexible enough to work with both internal and third-party toolchains.

“Automotive development isn’t slowed by coding — it’s slowed by configuration processes and tooling. FLYNC modernizes the process and tooling, turning it into an agile workflow that unlocks true shift-left development.” adds Dr. Lars Völker, Technical Fellow at Technica Engineering. “With the open-sourcing of FLYNC, we invite the industry into a collaborative effort — aligning on common challenges and building interoperable solutions for the automotive software ecosystem in a code-first approach.”

Beyond a technical solution, FLYNC represents a shift in mindset: treating configuration data as a strategic asset, not a byproduct of development.

FLYNC is an open-source project started by Technica Engineering, combining community-driven innovation with deep expertise in automotive systems and E/E architectures.

Learn more or get started: https://www.flync-language.com/…