Roadmap
Read this first
This is a statement of where openDAQ is investing and not a delivery commitment. There are no dates or feature names here and that is deliberate. A standard that misses published dates costs more trust than it ever buys. Compatibility does carry a commitment. Whatever lands, applications built today keep working with the devices they already reach.
Investment themes
None of these is finished and none has a date.
Broadening the set of protocols and profiles mapped into the common model so that a product that already speaks one of them can join the ecosystem through a shared integration rather than a product-specific device module.
Why it matters
Every protocol covered is a category of existing equipment that becomes reachable without its vendor writing anything.
Continued investment in openDAQ LT, the C stacks built to integrate into real-time operating systems, so that products with a small microcontroller and a tight power budget are not excluded from an ecosystem built around full SDK instances.
Why it matters
Constrained standalone measuring devices are where a lot of measurement value now sits. A model that only serves rack instruments is only half a model.
Keeping the SDK practical on the platforms vendors ship on including embedded Linux images, the supported language bindings and the build tooling that gets openDAQ into a product without a custom porting effort.
Why it matters
Adoption stalls on integration friction long before it stalls on capability. Reducing that friction is a roadmap item in its own right.
Extending the compliance lab and the certification programme around it so that an integrator planning a system reads tested results rather than marketing.
Why it matters
The value of the ecosystem is proportional to how much you can trust a compatibility claim without testing it yourself.
Investment in the tooling around the SDK so that the gap between connecting a device and understanding what it is doing stays as short as possible.
Why it matters
Most evaluations are won or lost in the first hour. Tooling is what makes that hour go well.
This is the least technical item here and arguably the most important. It means growing the number of products in the inventory across more vendors and more categories.
Why it matters
An interoperability standard is worth exactly what it connects. Every product added makes every existing integration more valuable.
Governance
Roadmap decisions are not made in public but they are not made arbitrarily either.
Dewesoft and HBK fund core development. openDAQ sets the direction itself with input from members, working groups and the public issue tracker.
Feature requests are prioritised by membership level. It is the most direct route for a company with a specific need and it reaches the people who decide.
Focused groups form around specific areas. Premium and Diamond members are invited to join them.
The SDK is public and so is its issue tracker. A well-argued issue from a non-member carries real weight. Several have.
What does carry a commitment
2–3
releases a year
A predictable cadence that product maintenance can be planned around and that is published openly.
Stable
API
Breaking changes are exceptional. When one is unavoidable the release notes explain what to do about it.
Backward
compatible by design
New applications are designed to work with older openDAQ devices and keeping an application current is what reaches newer ones.
Watch it happen
This page states intent. These are the places you can check what has genuinely shipped.
Where to find us
openDAQ attends test and measurement events through the year. Sometimes this is with a stand, sometimes on a founder's stand and sometimes as visitors. It varies by event.
If you are going to one then tell us and we will say whether we will be there too. Meeting in person is usually a better conversation than a call.
Next step
If openDAQ needs to go somewhere it is not going we would rather hear it from you than guess. A specific need from a real product carries more weight than a general request.