Driver development
Ground-up, two-way drivers built for how each platform actually works: native UI, proper feedback, graceful failure. Not a generic template with the logo swapped.
We build the code behind the connected home.
Suru is a specialist software house for home-automation integrations. We make devices fluent in every major control platform: reliably, natively, and to certification standard.
Fluent in
- TCP
- UDP
- RS-232
- IR
- ZigBee
- Z-Wave
- REST
- WebSocket
- mDNS
- SSDP
- MQTT
What we do
Device integration, end to end
From protocol analysis to certified release, we handle the whole lifecycle of a driver, so a device works the way the platform intended.
Protocol & API integration
We speak whatever the device speaks: documented APIs, serial protocols, local network control or cloud services, all implemented cleanly with the edge cases handled.
Multi-platform ports
One device, every ecosystem. We carry an integration across platforms with a shared core and platform-native behaviour on each, so features and fixes land everywhere.
Lifecycle & maintenance
Firmware moves, platform OSes move, and drivers rot without care. We keep releases versioned, regression-tested and current: for years, not launch week.
Platforms
Fluent in every major ecosystem
We build to each platform's native driver model and certification requirements, not lowest-common-denominator wrappers.
Control4DriverWorks driversIR · Serial · IP · Cloud · ZigBee · Z-Wave
SavantDevice profiles & integrationsIR · Serial · IP · Cloud
CrestronModules & Crestron Home driversIR · Serial · IP · Cloud · CEC · Cresnet
RTIIntegration Designer driversIR · Serial · IP · Cloud · ZigBee
URCTotal Control modulesIR · Serial · IP · Cloud · Z-Wave
Josh.aiNimble DevSuite integrationsIP · Cloud
Working with a platform not listed here? If it has an SDK (or even if it doesn't), talk to us.
Process
How an integration ships
Short, working-software cycles from datasheet to certified release. You always know where things stand, because you can see it running.
01
Scope
We map the device's capabilities to each platform's driver model (protocol, transport, feature set) and agree priorities. Enough to start building in days, with room for what the hardware teaches us.
02
Iterate
Development runs in short cycles against real hardware. A working driver lands early and grows every cycle (two-way state, error paths, reconnection logic), with builds you can try on a rack throughout.
03
Certify
Regression tests run from the first cycle, across firmware and platform OS versions, so certification is a checkpoint, not a surprise. We take the driver through each platform's review process where one exists.
04
Maintain
After release we track platform and firmware updates, ship versioned maintenance releases, and keep the regression suite running so nothing quietly breaks in the field, for as long as the driver is in service.
Approach
Engineering, not glue code
Drivers are small pieces of software that carry a big reputation: the installer's, the manufacturer's, and the platform's. We build them accordingly.
Tested on real racks
Every driver is developed and verified against physical devices and live controllers on our bench, because emulators don't have firmware quirks.
Built like real software
Version control, code review, changelogs and automated regression tests. A driver is a product with a lifecycle, and we treat it like one.
Native on every platform
Each ecosystem has its own idioms: UI conventions, event models, discovery. We build to them, so the integration feels at home on its platform. Native, never ported.
Straight answers
Clear advice on what's feasible, straightforward priorities every cycle, and progress you can see running. If something can't be done well, we say so before you've paid to find out.
Contact
Have a device that needs to speak?
Tell us about the device, the platforms you care about, and the timeline. We'll come back with a straight answer on approach, effort and cost.
- hello@suru.co
- Based in
- Brisbane, Australia