What is StormNode built with?
StormNode is being developed as a practical field node for the Planetnik network: it detects storm activity, collects environmental data, provides GNSS/GPS location context, captures sky images and sends telemetry to the project panel.
The main prototype board: Wi‑Fi/Bluetooth, OV2640 camera, firmware logic, photo handling, HTTPS upload and telemetry.
A lightning sensor used to detect local storm activity, estimated distance and raw lightning signal strength.
Environmental sensor for temperature, humidity and pressure. It adds weather context to storm events.
A Gravity GNSS GPS BeiDou receiver module supporting I2C/UART communication. In StormNode it provides location data, time context and support for synchronization and correlation in clusters.
Product photos and baseline hardware information for selected boards are based on public DFRobot materials: FireBeetle 2 ESP32-S3-U, Gravity Lightning Distance Sensor, Gravity I2C BME280. The GNSS/GPS module photo is based on public Botland product materials for DFRobot TEL0157.
Firmware and AI-assisted coding
We develop the firmware and project tools iteratively. Our development process also uses Codex by OpenAI and AI tools that support code analysis, software development, documentation and automation.
Changes remain under team control and follow the standard versioning and deployment process. The team is responsible for technical decisions, reviewing changes, hardware testing and final deployments.
Custom StormNode panel
We are also developing our own StormNode panel: events, photos, measurements, device status, history and archived data. The panel remains the operator layer, while selected community-facing data will flow through the API and realtime layer into Planetnik Cloud.
Planetnik Cloud
We are creating a separate community-facing layer at planetnik.cloud ↗. Its role is to present network growth, local observations, weather data, images and storm-activity context in a clear interactive form.
Hosting and server backend
The project has its own hosting backend based on dedicated servers and Linux systems, including Rocky Linux and openSUSE. This allows us to develop the API, panel, database, event archive and monitoring components without relying on a ready-made SaaS platform.
We use Proxmox Backup Server (PBS) to back up the project infrastructure and support recovery of environments and data in the event of a failure.
Infrastructure as Code
We maintain infrastructure configuration as code (Infrastructure as Code). We use Cinc to manage Linux server configuration automatically. Versioning configuration helps us control changes and recreate environments, while Zabbix supports service and infrastructure monitoring.
Infrastructure and project development
Planetnik Network extends beyond measurement devices. We give equal attention to the infrastructure that supports them. For users, this means a structured approach to developing services; for partners and contributors, it provides a shared, controlled process for working on the next parts of the network.
Source code for the website, panels, API and firmware is versioned in GitLab. We deploy changes through automated GitLab CI/CD processes and maintain infrastructure configuration as code (Infrastructure as Code). Cinc manages Linux server configuration automatically. Infrastructure components communicate through a private, encrypted network using WireGuard.
By versioning code and configuration and automating deployment, we are preparing the infrastructure to deploy further Planetnik Network components in a repeatable, controlled and scalable way. This makes it easier to recreate environments, track changes and grow the network as more nodes join.
-
Team and idea
The team develops and reviews changes, supported by AI tools.
Codex · AI-assisted development -
Versioned code
Application, API, firmware and configuration sources with change history.
GitLab -
Automation
Repeatable deployment of changes and configuration management.
CI/CD · IaC · Cinc -
Network growth
Infrastructure prepared for more Planetnik Network services and nodes.
Repeatability · scalability
WireGuard supports encrypted infrastructure communication.
Proxmox Backup Server (PBS) supports recovery of environments and data.
Technology for local nowcasting
StormNode data is designed to support future local nowcasting: analysis of current weather signals, telemetry trends, sky images and events detected by node clusters.
Technologies, tools and environment
Planetnik uses popular hardware, software and infrastructure technologies. The list below describes the project environment without suggesting partnership, certification or formal cooperation with the owners of the named brands.
Hardware and prototyping
Sensor modules and development boards used in StormNode prototypes.
The main StormNode device platform with Wi‑Fi, camera and C++ firmware.
Prototyping environment and libraries compatible with the Arduino ecosystem.
Node location plus time and synchronization context for clustered data.
3D design and printing
3D printer used for prototyping enclosures, holders, mounting parts and test components for StormNode.
Software for preparing models for printing, tuning parameters, splitting colors and controlling the prototyping workflow.
Firmware and programming
Supports the team in code analysis, software development, documentation and automation. Changes are reviewed and follow the standard versioning and deployment process.
Compilation and programming environment for StormNode firmware prototypes.
Main firmware language: sensors, camera, telemetry and communication.
Panel, API, event ingestion, photo upload and telemetry backend layer.
Web interface, information website, data presentation and UX elements.
Infrastructure and operations
Stable server environment for project services, web backend, API, panel and automation.
Linux system used in project workstations, testing or administrative environments.
Virtualization and infrastructure testing environment for project services.
Backups of the project infrastructure and recovery of environments and data in the event of a failure.
Hosting panel used in the web backend and test environments.
Versioning of website, panel, API and firmware source code and infrastructure configuration, alongside change history, issues and technical documentation.
Automated processes for deploying changes, linked to versioned code and team control.
Automated Linux server configuration management, supporting consistent and repeatable project environments.
Private, encrypted communication between project infrastructure components.
Monitoring of services, servers and infrastructure components supporting the Planetnik API, panel and test environments.
Repeatable approach to configuring servers, services and project environments.
Shared system layer for server services, administrative tools and infrastructure experiments.
Technology names, product names and trademarks belong to their respective owners. Planetnik uses them as parts of the project hardware, software or infrastructure environment. Mentioning a name does not imply partnership or certification.
What comes next?
Next steps include refining the outdoor enclosure, stabilising the firmware, expanding the panel, running field tests and inviting the first contributors into the pilot network.