ByteHive is the software foundation inside your gateway or site controller: Modbus and SunSpec device integration, on-site control logic, signed updates and fleet visibility. Your team builds only what makes your product different, or we build it for you from your spec, and you ship it under your name.
Where ByteHive sits: on your gateway, between your equipment and everything that uses its data.
Shipping today
SDK 1.0.0, released October 2026, with a sample gateway app as source.
Paid license
ByteHive is commercial software, not open source. You own the application layer you build. License terms on request.
Data out, built in
A documented JSON web API exposes your data model, devices, faults and history. No API to write.
Any protocol
Modbus TCP/RTU and SunSpec ship today. Need a different protocol? We typically have a connector working within a couple of weeks.
A fit if you want to ship your equipment connected, under your name. Modbus TCP and RTU, with SunSpec maps, ship today; any other protocol your equipment speaks, we connect by writing a connector. It feeds the same data model, so your logic, interface, cloud and updates work unchanged. Planned packaged connectors are on the Roadmap. Not in energy? Energy is our specialty, not the platform's limit: see Beyond energy.
The decision
Buy the foundation. Build what's different.
Every gateway or site controller needs the same groundwork before it does anything unique to you. ByteHive is that groundwork, already built. Build the rest yourself, or have us build it for you.
What you get
Connections to Modbus TCP and RTU equipment, with SunSpec maps for inverters, PCS and batteries included; other protocols through connectors we write for you
Real-time control logic that runs on site
A local web interface with user roles, plus fault and event logging
A built-in JSON web API to every value, device, fault and history, so your data is reachable from day one
A Modbus TCP server so your customer's SCADA or EMS can read the values you map to it
Signed updates with automatic rollback (Cortex-A76-class production image)
Fleet visibility in ByteHive Cloud
What you keep
Your brand and your product name
Your control strategy and user experience
Ownership of the application layer you build
Your own update-signing keys: you generate them
What you avoid
Writing a web API just to get your data out
Building device integration and data plumbing from scratch
Inventing a safe way to update units in the field
Writing your own fleet history and telemetry pipeline
Designing per-unit identity and encrypted connections yourself
Flexible by design
Don't like a protocol? We typically have a different one working within a couple of weeks.
Flexibility is a core design attribute of ByteHive. Protocols, devices, control logic and data access each change without rebuilding the rest.
Protocols
Modbus TCP/RTU and SunSpec ship today. For any other protocol your equipment speaks, such as EtherNet/IP, we write a connector that feeds the same data model.
Devices
Each device is described by a register map: configuration, not code. Add or swap equipment without new firmware.
Control logic
Change how a site behaves by swapping a script. Each script is fully checked before it runs; no firmware rebuild.
Your data
A built-in JSON web API gets your data out, and each value reports to the cloud on the schedule you choose.
Beyond energy
Energy first. Not energy only.
Our experience is in energy. The platform itself is general-purpose, so HVAC, building and home-automation gateways and controllers, and other data collection and control products, can be built on it too.
Modbus equipment, todayChillers, air handlers, heat pumps, drives and meters that speak Modbus can be described with register maps, the same way as energy equipment.
Other protocols, on requestBACnet or KNX for buildings; Zigbee, Z-Wave or Matter for homes. We write the connector; some also need a radio or interface on your hardware, which we scope with you.
Ready-made means energyThe SunSpec maps, the sample gateway app and ByteHive Cloud's built-in site views are all built for energy; no HVAC or home-automation maps are included. For your product, we scope the register maps, control logic and local web interface with you, or build them from your spec.
Risk
Built to reduce the risks that stall connected products.
Site safety
The site stays in control.
Control logic runs at the site, by design. The cloud observes and delivers approved updates; safety-critical commands are never cloud-writable. If the connection drops, the site keeps storing telemetry (7 days by default, configurable) and forwards it later.
Updates
A failed update rolls itself back.
Updates are cryptographically signed, installed beside the running version and kept only if a health check passes; otherwise the unit rolls back on its own. The site owner approves each install. Ships in our production image for Cortex-A76-class gateways.
Security
Security designed in.
Each unit creates its own identity key at the factory, and the key never leaves it. Mutual TLS to the cloud, HTTPS locally, role-based access, and an internal white-box review of the web API with identified issues remediated and re-tested.
Ownership
You hold the keys.
You own the application layer you build, and you generate your own update-signing keys. The SDK is delivered as source repositories with a manifest, and release builds are reproducible, with SHA-256 checksums.
Go to market
Three ways to ship under your name.
All three paths run on ByteHive, under a ByteHive license.
Path 1
Build on the ByteHive SDK
Choose this when your control strategy or user experience is what customers buy from you.
Edge runtime for x86_64 and ARM64 Linux
Control logic in scripts and state machines, without writing C; a C SDK and JSON web API when you want them
Simulators and a sample gateway app, so work starts before hardware arrives
ByteHive Cloud for fleet visibility and updates
Path 2
Start from the sample gateway app
Choose this to start from a sample application instead of a blank page.
CSS Gateway: a sample solar + storage gateway app, delivered as source with the SDK
Dashboard and power flow, device commissioning, per-device setpoints, faults and events, Modbus TCP for SCADA / EMS
Re-skin it with your logo, palette and product name, then extend it
Run only with simulators; not tested with any real equipment: you qualify it on yours. Site-wide strategies such as battery dispatch are not included
Path 3
We build it for you
Choose this to get your product built without growing your team. This is our core service.
Give us your spec: equipment, protocols, control strategy and user experience
CSS engineers build your gateway or controller on ByteHive, under your brand
Customization on request, including connectors for any protocol
Engineering billed hourly, against an estimate you approve; the ByteHive license for your product is separate
How your team works with ByteHive
1Connect devicesDescribe each Modbus device with a register map: configuration, not code. Other protocols get a connector.
2Design the logicScripts and state machines, or ByteHive Studio's visual canvas (developer preview).
3Ship safelySigned updates that roll back on their own if a health check fails.
4Run the fleetDevice inventory, faults and long-term history for every site in ByteHive Cloud. New device types need no cloud schema change.
ByteHive Studio · developer preview
Real screenshot: ByteHive Studio, where engineers draw control logic from standard blocks. Variable names masked.
Roadmap
What's real today, and what's next.
We keep the two clearly apart. Nothing in the right-hand column is shipping, and we don't publish dates here. If an item matters to your plan, ask us where it stands. Need a protocol today? We write connectors on request.
Shipping today
Edge runtime, SDK 1.0.0 (x86_64 and ARM64 Linux)
Modbus TCP and RTU devices; SunSpec maps (Common 1, Serial 17, DER 701–715, Battery 802)
Control logic: scripts, PID, filters, state machines
Local web interface with user roles
Signed updates with rollback (Cortex-A76-class production image)
ByteHive Cloud: live KPIs, long-term history, store-and-forward telemetry
Sample gateway app (CSS Gateway), included as source
Engineering services: we build your product from your spec, billed hourly
ByteHive Studio (developer preview)
On the roadmap Not shipping
Packaged protocol connectors: EtherNet/IP, CAN / J1939, DNP3, OCPP 2.0.1, OpenADR 2.0b, MQTT, Modbus RTU server
Packaged peak-shaving and battery dispatch apps
Load forecasting and VPP fleet aggregation
Remote setpoints from the cloud, accepted only where the site allows
Fully configurable ByteHive Cloud: views, history and retention set to your needs
Alarm notifications; team and organisation management
Studio: deploy and run designs on a device; live values
Hardware-rooted boot integrity; more hardware targets
Company
Built in Canada by CSS Inc.
ByteHive is built by Chokhawala Software Services Inc. (CSS Inc.), an embedded and edge software engineering company in Canada that also builds customers' products on ByteHive, from their spec. The sample gateway app, CSS Gateway, is built on the same platform we offer you. Your engineers get a 9-chapter developer guide, with examples compiled in CI, and a 14-chapter user manual; both publish measured behaviour and hard limits.
Measured on a Cortex-A76-class ARM64 gateway: a state machine reacts to a value change in 63 µs median (129 µs maximum observed). The data core passed an 8.47-billion-operation soak test with zero failures.
Bring your product plan and equipment list. We'll map them against what ships today and what's on the roadmap, and answer what your board will ask: who owns what, what you receive as source, how rebranding rights work, and what the ByteHive license covers and costs. If you want us to build it, we'll scope the work with you.
