Connect elevators, doors, barriers, sensors, charging piles and cameras of any protocol via configurable thing models, protocol plugins and parsing scripts — zero-code for standard protocols, one script for private ones — and orchestrate them with delivery, cleaning and inspection robots into automated workflows.
BS-IoT connects devices of any protocol and any type via thing models, protocol plugins and parsing scripts, and exposes standard APIs to upper-layer apps. Vendor clouds go through BS-Hub, robot assets are managed by BS-DCloud, and IoT devices are handled by BS-IoT — no system takes over another's device ledger.
Third-party vendor clouds are aggregated via open APIs and Webhooks. Hub only onboards and translates — it does not manage IoT devices.
BS-DCloud owns robot profiles, device shadows and command routing. It never takes over BS-IoT's device ledger, and vice versa.
Elevators, doors, barriers, sensors and cameras connect via protocol plugins, with their full lifecycle closed inside BS-IoT.
Three customer types, three answers, one platform foundation.
The hardest part of IoT onboarding isn't the protocol — it's starting from scratch for every device type. Before devices do any work, most of the budget is already gone.
Recommended: Professional / Enterprise
Recommended: Starter / Professional
Recommended: Starter / Enterprise
Generic IoT platforms stop at connectivity; we make devices actionable nodes in robot workflows — elevators, lights, auto-dispatch.
▎Elevators · lights · auto-dispatch
Thing model + protocol plugin + parsing script: zero-code for standard protocols, one script for private ones — onboarding shrinks from weeks to hours.
▎Zero-code standard onboarding
GraalVM sandbox with 4-dimension isolation; a failing script is contained and alerted without spreading or blocking other devices.
▎CPU ≤100ms · RAM ≤32MB
Hot 30 days / warm 1 year / cold archive with configurable retention — fast monitoring, complete analysis, economical compliance.
▎Hot 30d · warm 1y · cold archive
Open APIs + Kafka + HTTP callbacks + dashboards; device data flows back under authorization, with modular private deployment.
▎Query / invoke / subscribe APIs
Horizontally scalable gateways at ≥50k TPS per tenant — same architecture from dozens of devices to hundreds of thousands.
▎50k+ TPS per tenant
Robots unify in DCloud, vendor clouds go through Hub, IoT devices connect via BS-IoT protocols — upper apps consume each through its own API.
Property + event + service; 20+ preset templates to clone.
MQTT / HTTP / TCP / CoAP / Modbus / OPC UA / WebSocket.
Uplink decode / downlink encode in a sandbox with a simulator.
Direct / gateway sub-devices / API polling; single, Excel bulk, self-registration.
Thing models / protocols / scripts / devices / rules / open data — the full FR-IOT-01 ~ 06 scope
Tenants define their own product categories and clone from 20+ preset templates (charging piles, elevators, doors, cameras, sensors). The full TSL thing model defines properties, events and services — a service is an action the device can be asked to perform.
Robots wait at elevators; cross-floor delivery breaks the experience
Arrival event auto-calls the elevator to the current floor
Night cleaning needs manual lights and doors, switched off zone by zone
Start cleaning → lights and corridor doors on; finish → auto reset
PM2.5, noise and water-level exceedances are found by manual patrols
PM2.5 exceedance auto-creates inspection tasks with alerts and work orders
Fragmented Modbus/OPC UA devices, manual data logging, experience-based anomaly detection
Edge gateway collection → time-series storage → Kafka/HTTP to MES/ERP
Tenders demand building-control integration; no ready IoT stack
BS-IoT packaged with the robot solution with ready templates
| Dimension | Starter Device Onboarding | ProfessionalMost Popular Automated Operations | Enterprise Converged Operations |
|---|---|---|---|
| Ideal for | Vendor bundling, IoT pilots, read-only devices | Property/park automation, industrial collection | Robot+building operators, private deployments |
| Fleet scale | Thousand-device pilots | 10k-level via gateway aggregation | 100k-level, group/city scale |
| Protocol complexity | Zero-code standard protocols (MQTT/HTTP/TCP) | + Modbus/OPC UA/video/cloud APIs + private-protocol scripts | Professional + protocol plugin ecosystem |
| Automation depth | Threshold alerts → notifications | + visual rules, work-order loop, data forwarding | + robot orchestration, spatial resource linkage |
| Parsing scripts | — | Script center + simulator | Same as Professional |
| Robot integration | — (custom via open APIs) | Custom via open APIs | Ready mixed scenarios (elevators/lights/dispatch) |
| Data openness | Property query / event subscription | + Kafka/HTTP/TSDB forwarding, dashboards | + private intranet integration |
| Deployment | SaaS | SaaS | SaaS / Private |
Device Onboarding
Vendor bundling, IoT pilots, read-only devices
Automated Operations
Property/park automation, industrial collection
Converged Operations
Robot+building operators, private deployments
Tell us your device types and protocols — we'll reply with an onboarding assessment within 1 business day.
50k+ TPS per tenant · sandbox CPU ≤100ms · hot 30d / warm 1y / cold archive · SaaS & on-premise
Some interface images above are system mockups, not actual screenshots. The actual system UI is as demonstrated by our sales team.
