Quick search…
Router Firmware Services
Getting started
OpenSource
Deploy and operate Network Devices using Open-Source Components and a Simple Interface.
OpenZen is all about managing network devices running Openwrt via the network (or the internet). This process is split into two principal parts:
communicating with the backend that supplies the configuration and,
implementing the configuration on the router. Between these two lies an abstraction - a ubus interface - which allows their implementations to be swapped out.
For instance, OpenZen provides a HTTP interface for obtaining the configuration and firmware updates and providing metrics but users are free to use and create implementations that are more tailored to their needs, maybe using Websockets, MQTT, or protobuf.
On the other side of the ubus interface, services react to configuration objects by listening to ubus events. Wireless, typical network setups, and updates are provided for by OpenZen. The device configuration is a JSON object, so users can configure their own services by adding more objects to the configuration.
Beware: The open-sourcing is still in progress. Not everything is written in stone.
Deploy and operate Network Devices using Open-Source Components and a Simple Interface.
OpenZen is all about managing network devices running Openwrt via the network (or the internet). This process is split into two principal parts:
communicating with the backend that supplies the configuration and,
implementing the configuration on the router. Between these two lies an abstraction - a ubus interface - which allows their implementations to be swapped out.
For instance, OpenZen provides a HTTP interface for obtaining the configuration and firmware updates and providing metrics but users are free to use and create implementations that are more tailored to their needs, maybe using Websockets, MQTT, or protobuf.
On the other side of the ubus interface, services react to configuration objects by listening to ubus events. Wireless, typical network setups, and updates are provided for by OpenZen. The device configuration is a JSON object, so users can configure their own services by adding more objects to the configuration.
Beware: The open-sourcing is still in progress. Not everything is written in stone.
Deploy and operate Network Devices using Open-Source Components and a Simple Interface.
OpenZen is all about managing network devices running Openwrt via the network (or the internet). This process is split into two principal parts:
communicating with the backend that supplies the configuration and,
implementing the configuration on the router. Between these two lies an abstraction - a ubus interface - which allows their implementations to be swapped out.
For instance, OpenZen provides a HTTP interface for obtaining the configuration and firmware updates and providing metrics but users are free to use and create implementations that are more tailored to their needs, maybe using Websockets, MQTT, or protobuf.
On the other side of the ubus interface, services react to configuration objects by listening to ubus events. Wireless, typical network setups, and updates are provided for by OpenZen. The device configuration is a JSON object, so users can configure their own services by adding more objects to the configuration.
Beware: The open-sourcing is still in progress. Not everything is written in stone.
Deploy and operate Network Devices using Open-Source Components and a Simple Interface.
OpenZen is all about managing network devices running Openwrt via the network (or the internet). This process is split into two principal parts:
communicating with the backend that supplies the configuration and,
implementing the configuration on the router. Between these two lies an abstraction - a ubus interface - which allows their implementations to be swapped out.
For instance, OpenZen provides a HTTP interface for obtaining the configuration and firmware updates and providing metrics but users are free to use and create implementations that are more tailored to their needs, maybe using Websockets, MQTT, or protobuf.
On the other side of the ubus interface, services react to configuration objects by listening to ubus events. Wireless, typical network setups, and updates are provided for by OpenZen. The device configuration is a JSON object, so users can configure their own services by adding more objects to the configuration.
Beware: The open-sourcing is still in progress. Not everything is written in stone.
Deploy and operate Network Devices using Open-Source Components and a Simple Interface.
OpenZen is all about managing network devices running Openwrt via the network (or the internet). This process is split into two principal parts:
communicating with the backend that supplies the configuration and,
implementing the configuration on the router. Between these two lies an abstraction - a ubus interface - which allows their implementations to be swapped out.
For instance, OpenZen provides a HTTP interface for obtaining the configuration and firmware updates and providing metrics but users are free to use and create implementations that are more tailored to their needs, maybe using Websockets, MQTT, or protobuf.
On the other side of the ubus interface, services react to configuration objects by listening to ubus events. Wireless, typical network setups, and updates are provided for by OpenZen. The device configuration is a JSON object, so users can configure their own services by adding more objects to the configuration.
Beware: The open-sourcing is still in progress. Not everything is written in stone.
cloud-tunnels
© Copyright 2024 All rights reserved.
Getting started
OpenSource
Deploy and operate Network Devices using Open-Source Components and a Simple Interface.
OpenZen is all about managing network devices running Openwrt via the network (or the internet). This process is split into two principal parts:
communicating with the backend that supplies the configuration and,
implementing the configuration on the router. Between these two lies an abstraction - a ubus interface - which allows their implementations to be swapped out.
For instance, OpenZen provides a HTTP interface for obtaining the configuration and firmware updates and providing metrics but users are free to use and create implementations that are more tailored to their needs, maybe using Websockets, MQTT, or protobuf.
On the other side of the ubus interface, services react to configuration objects by listening to ubus events. Wireless, typical network setups, and updates are provided for by OpenZen. The device configuration is a JSON object, so users can configure their own services by adding more objects to the configuration.
Beware: The open-sourcing is still in progress. Not everything is written in stone.