FLYNC (FLexible Yaml-based Network Configuration), an open-source, repository-native solution that turns vehicle network configuration into clean, version-controlled code.
The heart of FLYNC is a single, human-readable model schema together with a comprehensive SDK that lets you create, validate, and manipulate configurations programmatically.
By organizing system definitions in a central, version-controlled repository, this tool helps engineering teams manage complexity, enable reuse, and maintain consistency across domains.
Purpose-built for automotive networks, the language models configurations across multiple abstraction layers, enabling early detection of inconsistencies and integration issues.
Bring modern software engineering practices to configuration management:
- Git-based version control and workflows
- CI/CD pipeline integration for automated validation
- Traceability and reproducibility across releases
Highly optimized validation and parsing logic allow the library to handle large-scale configurations with high and predictable performance.
Designed for usability and rapid adoption:
- Intuitive, readable syntax
- Clear and structured documentation
- Suitable for domain experts, software & network engineers
Released under an open license to encourage:
- Community contributions
- Ecosystem integrations
- Extensibility for emerging automotive needs
Contributions and feedback are welcome.
A minimal dependency footprint makes the library easy to:
- Embed into existing tooling
- Distribute across environments
- Automate within automotive development pipelines
FLYNC is designed for:
- E/E architecture teams.
- Network and platform engineers.
- SDV DevOps and integration teams.
- Validation and test engineers.
- Toolchain and automation specialists.
FLYNC is open source under the Apache-2.0 license, and thrives on community input! We welcome:
- Bug reports - Open an issue with a clear description and minimal reproducible example.
- Feature requests - Propose new models, validation rules, or SDK adaptions.
- Pull requests - Follow the standard GitHub flow: fork, feature branch, commit, PR.
- Documentation improvements - Keep the docs up-to-date and user-friendly.
Apache License Version 2.0