Electronic trading today is a marvel of engineering. Exchanges operate as distributed systems, speaking in low-level protocols that demand precision. Yet for all this sophistication, some firms find themselves reinventing the wheel, building infrastructure in isolation, duplicating effort, and debugging the same problems repeatedly.
Two initiatives, STAC and the Open Markets Initiative (OMI), emerged to change that. Both treat technical knowledge as a public good. Both transform understanding into infrastructure. And both show how neutrality and collaboration can raise the quality of the entire financial ecosystem.
The Origins of STAC
STAC began in 2007 with a simple idea: measuring performance in finance with consistency and transparency. Member-driven benchmarks provided a neutral framework where results could be trusted.
However, the benchmarks themselves were never the end goal. Their deeper value lay in what they enabled:
- Engineers could compare methods on equal footing.
- Patterns emerged across systems and approaches.
- Teams improved not in isolation, but together.
We believe STAC has cultivated a culture of reproducible understanding, a scientific mindset applied to finance. That spirit continues through the STAC Summits. At these gatherings, practitioners test assumptions, discuss techniques, and build trust in a setting designed for technical honesty. In this way, STAC has become not just a benchmarking body, but a community of practice, where science and collaboration reinforce one another.
The Parallel Origins of OMI
The Open Markets Initiative was born from a different but equally pressing challenge. Every firm was decoding the same FIX and binary market data feeds independently. Documentation, primarily in the form of PDFs, was dense, inconsistent, and often incorrect.
OMI’s breakthrough was to model exchange protocols formally. From these models, software could automatically generate:
- Parsers and dissectors
- Documentation and data pipelines
- Database ingestors and debugging tools
When a specification changes, every derived tool updates with it, removing bugs and maintenance effort.
One of OMI’s most practical contributions is its library of Wireshark dissectors, generated directly from these specifications. Many firms rely on them to debug packet captures and diagnose system issues. Because the dissectors are open source, they are constantly tested against real-world data. Bugs are reported, fixed, and folded back into the specifications, turning every failure into a refinement of collective protocol knowledge.
In this way, OMI has evolved from a toolset to a knowledge base for technical trading, where shared models replace fragmented interpretations.
Neutrality as a Condition for Trust
Both STAC and OMI succeed because they are neutral.
- STAC’s benchmarks are credible precisely because no single vendor controls them.
- OMI’s specifications are trusted because they reflect crowd-observed behavior, not one firm’s interpretation.
Neutrality lowers the barrier to participation. It ensures that shared accuracy serves the market as a whole, not private advantage. This allows each organization to host its own kind of technical commons that everyone can build upon.
The Community Component
Both STAC and OMI succeed because they are a community. They each provide enabling layers for collaboration, and that collaboration produces a sum greater than its parts.
If you want to get the most out of these communities, you can help them and further your own projects by participating. Here’s how:
- Join STAC’s special interest groups or attend its conferences.
- Use OMI’s dissectors when diagnosing problems.
- Read the knowledge base articles and repositories.
- Report what you find and contribute back.