Modern Out-of-Band Management for Network ResilienceSecure access · edge software · ZERO cloud visibility
Embedded Linux Software Platform

GearlinuxSoftware built to keep evolving.

A modern embedded Linux platform for resilient network, edge, and OEM products. Gearlinux combines an immutable firmware foundation, open-source technology, Gearlinx software IP, secure lifecycle management, automation, containers, and cloud or local management in one adaptable platform.

Grounded in more than two decades of embedded Linux development, beginning with uClinux in 1998.
Gearlinx gear iconGEARLINUX / PLATFORM STATUS
Current
gearlinux@edge:~$ platform status
firmware immutable image
lifecycle rolling updates + security review
management ZERO cloud / HTTPS / SSH
automation REST API / ZTP / Python*
workloads OCI / Docker containers*
oem customer IP + OSS + Gearlinx platform
status ready for supported platforms
ImmutablePredictable software state
Cloud + LocalFlexible management model
OEM ReadyAdaptable software foundation
Immutable FirmwareControlled software state
Rolling ReleasesBug + security updates
Open-Source FoundationManaged licensing + compliance
Cloud + Local ManagementZERO / HTTPS / SSH
OEM Software PlatformAdapt to new hardware
Why Gearlinux

Stop treating embedded software like a one-time build.

Products live for years. The software inside them has to keep up with security fixes, new protocols, new applications, changing hardware, and new customer requirements without turning every update into a major engineering project.

01
Long-term maintainability

Gearlinux is continuously evolved so supported products can stay current instead of accumulating avoidable technical debt.

02
Security-minded lifecycle

Key packages and public security issues are reviewed as part of the ongoing software lifecycle and firmware release process.

03
Build with open standards

Linux, open-source software, APIs, containers, and familiar management interfaces create a flexible base for product development.

04
Customize without starting over

OEM programs can combine customer IP, open-source components, and the Gearlinx software foundation around a target product.

Gearlinux Architecture

A practical software stack with clear ownership.

Gearlinux projects are designed to combine the pieces a product needs without confusing who owns what.

Layer 3Customer proprietary code

Customer applications, product logic, algorithms, or other proprietary software can remain customer intellectual property.

Layer 2Gearlinx platform components

Applications, hardware configuration, configuration schema, management frameworks, and other Gearlinx software IP.

Layer 1Open-source software

Linux kernel and other OSS packages retain their applicable open-source licenses and are managed as part of the complete build.

One integrated system, not a pile of packages.

Gearlinux is built around Linux and extensive use of open-source software, with Gearlinx integrating, testing, maintaining, and packaging the complete system for supported hardware.

Current Gearlinx materials reference technologies including BusyBox, OpenVPN, WireGuard, modern WebUI and CLI management, IPv4/IPv6, serial logging, and OpenID-based single sign-on on supported products.

The objective is simple: give product teams a software foundation they can build on, maintain, secure, and evolve over the life of the product.
Core Capabilities

Embedded software built for operations.

The exact feature set depends on hardware and project scope, but Gearlinux provides a mature foundation for resilient, connected products.

IMM

Immutable firmware

A controlled firmware image helps create a predictable software state and a cleaner approach to upgrades, rollback planning, and support.

SEC

Security + updates

Gearlinx reviews important packages and publicly announced security issues, then incorporates fixes and updates into the supported software lifecycle.

API

Automation + APIs

Supported Gearlinx platforms use REST API, Zero Touch Provisioning, Python, and structured management interfaces to automate deployment and operations.

OCI

Containers + applications

OCI and Docker container support on supported platforms lets teams add applications and services without rebuilding the entire embedded system around each workload.

NET

Networking + secure access

Gearlinux integrates the networking, VPN, remote-access, logging, and device-management functions needed to support connected edge and network products.

UI

Modern management

Manage supported systems through cloud workflows, a local structured HTTPS interface, or SSH-based command-line access depending on the deployment model.

Cloud + Local Management

Manage the software where the operations team works.

Gearlinux can operate as a standalone firmware platform, while ZERO adds centralized management for organizations that want visibility and control across devices, sites, and fleets.

01
Provision + configurePush configuration or settings to individual devices or groups from a centralized workflow.
02
Upgrade firmwareUse the management platform to keep deployed systems current and simplify software lifecycle operations.
03
Report + supportTrack device status, location, serial numbers, subscription information, metrics, and support context where applicable.
04
Stay flexibleLocal HTTPS and SSH options support systems that do not need or cannot use a cloud-first operating model.
Gearlinx ZERO cloud dashboard on a laptop
OEM Software Platform

Bring your hardware. Do not start the software from zero.

Gearlinux can be adapted as an OEM embedded-software foundation for companies building connected network, industrial, power, edge, or infrastructure products. The commercial model can be structured around the target hardware, software scope, support, and optional cloud services.

What the OEM gets

A mature Linux foundation, hardware enablement, management framework, secure update discipline, reusable networking and application components, and engineering experience that can shorten the path from prototype to production.

STEP 01
Define the product

Target hardware, interfaces, protocols, product behavior, management model, and customer experience.

STEP 02
Adapt Gearlinux

Enable the hardware platform and extend the software around the product requirements.

STEP 03
Integrate customer IP

Add customer applications and product-specific logic while preserving clear IP boundaries.

STEP 04
Ship + maintain

Move into production with an ongoing software, security, update, and support strategy.

CustomerProprietary code

Typically remains the customer's intellectual property.

Open SourceLinux + OSS

Remains governed by applicable open-source licenses.

GearlinxPlatform IP

Gearlinx applications, configuration, schema, management, and other proprietary components.

OEM Proof Point

Gearlinux has already moved beyond Gearlinx-branded hardware.

For Advanced Converter Solutions, Gearlinux was expanded for a new hardware architecture and software requirements around DC/DC converter management. The project demonstrates the platform's ability to support OEM development rather than being limited to a fixed console-server image.

Read the OEM deployment story →
Up to 96 convertersThe ACS project centered on managing a large DC/DC converter stack.
CAN Bus + ModbusGearlinux was extended to support additional industrial interfaces and protocols.
Time-series + graphingThe software scope included storing and visualizing operational data over time.
Standalone + optional cloudThe deployment supports standalone firmware with an opt-in cloud management model.
Software Lifecycle

The product ships once. The software has to keep moving.

Gearlinux is maintained as an evolving platform rather than a frozen code branch that gets harder to support every year.

Review

Monitor key packages, upstream changes, public vulnerabilities, and critical software dependencies.

Integrate

Bring selected kernel, library, application, bug, and security updates into the supported Gearlinux build.

Test

Validate the complete firmware system against supported platforms and release requirements.

Release

Deliver firmware updates and new capabilities through the supported product or OEM lifecycle.

Gearlinx Ecosystem

One software foundation across the platform.

Gearlinux is the embedded software layer underneath Gearlinx hardware, with ZERO providing the centralized cloud-management layer.

High-Density Platform

NR4400

Gearlinux powers the NR4400 software environment, including Total OOB® management, modern GUI/CLI, automation, containers, edge compute, and secure remote access capabilities on supported models.

Compact Cellular Platform

Duckfone

Gearlinux provides the software foundation for compact cellular OOB deployments with local management, secure access, serial logging, automation, and ZERO integration.

Cloud Management

ZERO

ZERO centralizes provisioning, device and location management, reporting, firmware lifecycle, fleet operations, and other cloud-managed workflows around supported Gearlinux systems.

Gearlinux FAQ

Common questions about the software platform.

Answers about Gearlinux, OEM deployment, lifecycle management, and how the platform fits with Gearlinx products.

Gearlinux is Gearlinx's embedded Linux software distribution and firmware platform. It provides the operating-system foundation, device management framework, networking, security, automation, and integration capabilities used across Gearlinx hardware and supported OEM projects.

Yes. Gearlinux firmware is delivered as an immutable image. This approach helps create a predictable software state and supports controlled firmware upgrades rather than allowing the underlying operating-system files to drift over time.

Gearlinx reviews key packages, monitors security issues, and delivers regular rolling releases with bug fixes, security updates, and new capabilities. Critical fixes can be handled outside the normal release cycle when urgency requires it.

Yes. Gearlinx can adapt Gearlinux as an OEM embedded-software foundation for supported third-party hardware. OEM projects are scoped around the target hardware, required interfaces, applications, management model, and commercial support requirements.

Gearlinux projects can combine customer proprietary code, open-source components, and Gearlinx proprietary platform components. Customer proprietary code typically remains customer intellectual property, open-source software retains its applicable licenses, and Gearlinx platform components remain Gearlinx intellectual property unless a project agreement states otherwise.

No. Gearlinux can support local HTTPS and SSH-based management, while ZERO adds centralized cloud management, provisioning, firmware lifecycle, reporting, device visibility, and fleet operations. OEM projects can also be designed with an optional cloud model where appropriate.

On supported Gearlinx platforms, Gearlinux supports OCI and Docker containers, REST API workflows, Zero Touch Provisioning, and Python-based automation. The exact feature set for an OEM implementation depends on the target hardware and project requirements.

Gearlinux is the software foundation used on Gearlinx NR Series and Duckfone products. It has also been extended for an OEM customer deployment on a different hardware architecture, demonstrating that the platform can be adapted beyond Gearlinx-branded appliances.

Build your next product on a software foundation that already knows how to evolve.

Talk with Gearlinx about Gearlinux for Gearlinx infrastructure, embedded software development, or an OEM platform that needs a faster path from prototype to production.