What we build
Most projects fall into one of six areas. They usually overlap — a smart home controller speaks Bluetooth to sensors, Wi-Fi to the cloud, and serial to a legacy panel — and the same base library handles all of them.
Bluetooth, Classic and Low Energy
Applications that pair with peripherals and exchange data. GATT client and server implementations. OBEX profiles for file transfer and object push. Audio control — switching endpoints, reading and setting volume, running a PC as an A2DP receiver.
Support for non-standard stacks (BlueSoleil, Toshiba) and the BLED112 USB dongle when the native Windows driver is not enough. BLE beacons: receiving, decoding, and transmitting advertisement packets, including Extended Advertising for Bluetooth 5.
Wi-Fi and Wi-Fi Direct
Applications that manage networks, not just connect to them. Enumerating and switching profiles. Creating software access points — SoftAP, legacy Hosted Network, or the Windows Mobile Hotspot — with fine-grained control over who connects.
Capturing raw Wi-Fi frames for analysis. Reading and writing driver-level parameters, including band selection on dual-band adapters. Integration with the Windows Network List Manager for tracking every interface and connection on the machine.
Serial communication
COM, UART, and RS232 on Windows and macOS. Enumerating ports and USB devices, monitoring for hardware changes, handling modem events, and driving signal lines.
Full OBEX implementation on top of serial transport, for devices that use it as their wire protocol. Support for virtual COM ports — USB, Bluetooth, and com0com.
IoT firmware
Firmware for Arduino, ESP32, and ESP8266. Sensors, actuators, displays, and radio modules. Cloud integration over MQTT, HTTP, or WebSockets. Over-the-air updates. Power budgets that match the hardware — every milliwatt matters when the device runs on a coin cell.
This is where the desktop side of the stack meets the embedded side, and we build both.
Smart home
Automation systems for residential spaces — lighting, climate, curtains, and sensor networks. Custom controllers and hubs based on ESP32 or Arduino.
Integration with voice assistants: Google Assistant, Amazon Alexa, Yandex Alice, Apple Siri. Sensor monitoring for temperature, humidity, motion, and door state. Desktop and mobile applications for the person who runs the system every day.
Industrial automation
We have delivered systems that run quietly at factories and in offices — equipment monitoring, data collection from legacy panels, and wireless bridges between machines that were never designed to talk to each other.
Serial to Ethernet, Bluetooth to cloud, custom protocol gateways. Where commercial products already exist, we build the layer that ties them into your existing infrastructure.
Why us
Most software shops that claim wireless expertise are using the same public APIs everyone else uses. That is fine for a simple integration. It is not fine when the device you need to talk to has a firmware bug, or when the OS version you have to support dropped a feature two years ago.
We have twenty years of depth in exactly this problem. Not as a service — as the core of the business. The libraries behind your project were written to solve the same class of problems for thousands of other developers, and every bug we have already found in that code is a bug your project will not have to find.
Every engagement runs full cycle: design, prototyping, implementation, testing on real hardware, and long-term support. We work on fixed price, hourly, or outsourcing arrangements — whichever fits your budget and your planning process. All intellectual property transfers to you at the end.
How we work
- Discussion. You describe the problem, the hardware, and the constraints. We respond with possible approaches — including the ones we would not recommend, and why.
- Estimation and plan. A short technical proposal with a timeline, a cost, and a breakdown of stages. No hidden work items.
- Prototype. Before committing to the full build, we prove the risky part works. If the radio behaves differently than expected, we find out here — not three months in.
- Implementation. The full application, built on the same libraries we ship. Tested against real devices, not emulators.
- Support. Updates, bug fixes, and adjustments as the platform moves. Frameworks you depend on are maintained by the same team, so support does not depend on a third party.
Start a conversation
Tell us what you are building. A short description of the device, the platform, and the problem is enough to begin. We will respond within one business day — usually with a question or two, then a proposal.