Skip to content
Oguzhan KAYNAK edited this page Nov 15, 2026 · 10 revisions

WireForge

Match your wire format byte for byte. Define the wire format and interface (in YAML by hand, in the web UI, through the CLI or an AI agent) and generate heap-free C++17 or C99 code that implements it: serializers, validators, framers and dispatchers, with a GoogleTest project that checks them against a reference codec.

Generated code never adds bytes, and it uses only pre-allocated storage (no heap, no exceptions, no RTTI required). Only your side needs WireForge: the other end can be hardware, an autopilot or another team's code. Describe a whole system of units in one model and each unit gets only its own code, tests and documents.

WireForge in one minute (video)

On a real board: the generated C code on an STM32, talking MAVLink 2 to pymavlink.

Where to go

  • Tutorial: twelve chapters around one MAVLink 2 drone link and a system of several units, from the model to a vehicle in C++, C and Rust that talks to pymavlink, firmware on a Cortex-M4 and a real STM32 board, ArduPilot's simulator, tests, CI, Wireshark and AI agents
  • Getting Started: install, first project, first generated code
  • Protocol Library: ready-made models (Modbus, CRSF, J1939, MAVLink 1 and 2, UBX) and what each was checked against
  • Importing: CSV/Excel ICDs, C headers, CAN databases (DBC)
  • Integrations: GitHub Action, Wireshark dissector, MCP server, web UI
  • FAQ: license, supported languages, common problems
  • How it compares: protobuf, nanopb, Kaitai Struct, mavgen, cantools

The technical reference lives in the repository: docs/.

Clone this wiki locally