Binary Protocol Documentation
Bytes don't lie. But your documentation might.
When your protocol spec uses prose to describe byte layouts, consumers fill in the gaps with assumptions. OptiByte makes the byte layout the documentation — interactive, precise, and always in sync.
The precision problem
- Prose descriptions of byte layouts are inherently ambiguous.
- Consumers interpret differently. Some get it right. Others build against wrong assumptions.
- By the time you find the bug, hardware is already deployed.
- Every edge case your spec didn't cover becomes a support ticket.
What OptiByte changes
- Define the exact byte layout once — field offsets, lengths, data types, constraints.
- Generate interactive documentation where consumers can explore field behavior.
- Provide a sandbox to test payloads before implementing against the real protocol.
- When the protocol changes, documentation updates automatically from the same source.
Byte-Level Precision
Every field has an exact offset, length, and data type. No prose ambiguity, no gaps for interpretation.
Interactive Field Explorer
Consumers can click on any field to see its constraints, valid ranges, and relationships to other fields.
Payload Sandbox
Test any payload against your protocol definition before building. Catch issues in the design phase.
Automatic Sync
Documentation stays in sync with your protocol definition. No more outdated docs floating around.
Turn your byte layout into your documentation
Start by defining one message structure and see how OptiByte transforms your protocol delivery.