[Open-source] A "zero-code invasive" enterprise-level IoT platform built on a Java technology stack
![[Open-source] A "zero-code invasive" enterprise-level IoT platform built on a Java technology stack](https://yy123.ink/api/img/1782579785138-p84a6e.jpg)
1. Project Overview
NexIoT IoT Platform
A Java technology stack-based "zero-code intrusion" enterprise-level IoT platform
NexIoT IoT is a Java technology stack-based "zero-code intrusion" enterprise-level IoT platform, with high cohesion and low coupling, zero-code intrusion. The platform integrates cloud debugging functions, supports TCP, MQTT, Tianyi IoT, HTTP, etc. Multiple protocols for unified management, providing complete product definition, device model design, device access, northward application output, rule engine, etc. Core functions, providing a one-stop solution for IoT applications; complete open-source, import and run!
2. Open Source License
Licensed under AGPL-3.0
3. Screenshots
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
4. Feature Overview
✨ Based on Java21 "zero-code intrusion" enterprise-level IoT platform, supporting multiple protocol direct connection, cloud debugging, configuration! Supports TCP direct connection, MQTT direct connection, Tianyi IoT (AIoT), HTTP REST, etc. Multiple device access methods, meeting different scene needs Based on browser real-time protocol development and debugging, supporting online testing, hot deployment, making protocol development more efficient!!Platform Highlights
-
✅ Low-cost connection: Access a device with an external debugger, no need to modify any system code, no code intrusion, a university student can complete. -
✅ All components remain: TCP, MQTT, Tianyi IoT, etc. Enable as needed, it's easy to connect a new platform. -
✅ No standardized response to various standards: Domestic industry protocol status, no longer standardize, focus on responding to various standards access, looks very complex and unclear, easy to use. -
✅ Powerful protocol debugger: Based on browser real-time protocol development and debugging, direct device access has not been restarted for half a year. -
✅ Simplified architecture: Java21, mysql5.7+, redis, MQTT (not limited to emqx or other), easily handle millions of devices; supports clickhouse storage (configuration only)
Core Function
Device access ability
-
✅ TCP device access: 16-bit message transmission, protocol parsing, cloud debugging, online testing -
✅ MQTT device access: Device model/transmission mode, cloud debugging, online testing, supports EMQX/HiveMQ, etc. -
✅ HTTP device access: REST API, Java SDK, OAuth2 authentication, complete interface specification -
✅ Tianyi IoT Connection: Device registration, data reporting, command issuance, standard protocol interface -
✅ Cloud Cloud Connection: Already supported, with complete SDK and API, supporting multi-platform data synchronization, protocol conversion
Core Management Function
-
✅ Product management: Multi-protocol product creation, device model definition, product label, public configuration -
✅ Protocol Management: Cloud debugging environment, pluginized architecture, real-time protocol development, unified management platform -
✅ Device Management: Device detail monitoring, online command issuance, device shadow, message subscription, log viewing -
✅ Network Component: TCP/MQTT service management, start/stop/disable operation, personalized parameter configuration -
✅ Application Management: Northward application output, OAuth2 API SDK, device binding, push configuration -
✅ Notification Management: Multi-channel support (Dingding, Aliyun, Tencent Cloud, webhook, email, Feishu) -
✅ Scene linkage: Trigger rules based on device attributes/events, multi-action execution, real-time automation - RuleGO Rule Engine
: Visual rule engine execution, supporting OPCUA, Moudbus industrial scene
Protocol Access Status
|
Protocol Type |
Status |
Core Function |
|
TCP Device |
✅ Implemented |
Hexadecimal message transmission, protocol parsing, cloud debugging, online testing |
|
MQTT Device |
✅ Implemented |
Device model/transmission mode, cloud debugging, online testing, supporting EMQX/HiveMQ etc. |
|
HTTP Device |
✅ Implemented |
REST API, Java SDK, OAuth2 authentication, complete interface specification |
|
Tianyi IoT |
✅ Implemented |
Complete product creation, device registration, data reporting, command issuance, standard protocol interface |
|
Cloud-to-cloud interface |
✅ Supported |
Java SDK self-extended protocol module |
5. Tech Stack
Architecture Diagram

Deployment Diagram

Quick Start
Environment Requirements
- JDK
21+ - MySQL
5.7+ - Redis
6.0+ - Maven
3.9+
Technical architecture
Technical Stack
- Backend Framework
Java 21 SpringBoot 3.5 Tk.Mybatis 5.0.1 - Data storage
MySQL5.7+ / Redis / ClickHouse (optional) - Architecture Pattern
Monolithic Architecture Design, Supporting Microservices Deployment - Front-end Technology
Built with RuoYi-Antdv, thank you to the open-source community!

























