Branded hardware
Present the gateway as part of your product family.
- Custom enclosure color and marking
- Customer device identity
- Packaging and installation materials
White-label partner programme
Your brand. Your cloud. mini-OTG underneath.
Add field connectivity to your platform without building another cloud in the middle, writing every device driver yourself, or putting a third party between you and your customer.
Discuss an OEM programmeA product layer you can own
Customize the parts your customer sees.
The protocol work stays underneath. Everything above it bends to your commercial, operational and security model.
Branded local setup
Installers see your platform, not ours.
- Your logo, colors and language
- Setup flows built for your field teams
- Equipment profiles already loaded
Pre-provisioned cloud
Gateways arrive knowing where to connect.
- Endpoint and schema presets
- Your certificates and credentials
- A provisioning workflow that scales to a fleet
The hardware
Your name goes on the front.
A four-module DIN-rail gateway for the meter cabinet. The front label keeps an area for your brand, and the QR code carries the device identity you provision.
- Top
- Ethernet and HAN (RJ45), P1 (RJ12)
- Front
- Status LEDs, your label, USB-C service port
- Bottom
- Power, RS-485 and relay terminals
- Back
- 35 mm DIN rail
Enclosure study, not a frozen production form factor. Label marks show reserved positions; certification is pending.
Partner workflow
From integration scope to controlled rollout.
We shape the programme around your equipment, your data contract and the way you actually run a fleet.
Define
Agree the equipment, the cloud interfaces, the volumes and who owns what.
Integrate
Build and check the device profiles, payload mapping, provisioning and branded setup.
Evaluate
Run controlled evaluations on sites that look like your real ones.
Prepare
Freeze the production requirements, certification scope and commercial terms.
Clear ownership
Your platform stays in front.
We supply the device and protocol layer, and nothing above it. Your cloud stays the EMS, the CSMS, the optimization service, the application the customer logs into.
Your brand
Hardware identity, setup language, support path.
mini-OTG
Drivers, normalization, security, delivery.
Your platform
Data ownership, applications, control, billing.
Build the gateway into your offer
Discuss your product →Start with one concrete deployment profile.
Tell us what you need to connect, where the data has to land, and whose name should be on the box.