Contiki-NG

Contiki-NG is a free, open-source operating system for low-power IoT devices, best suited to developers building constrained edge nodes around standard networking protocols. Its configurable memory footprint and broad protocol stack make it a strong candidate for tight hardware budgets; check its documented board and link-security support before committing to a target.

Overview

Contiki-NG is built for devices where memory is a hard constraint: its code footprint is on the order of 100 kB, and memory use can be configured as low as 10 kB. That makes it relevant for low-power nodes that cannot spare the resources of a larger operating system. The narrow focus is also a boundary: this is an embedded IoT platform, not a general-purpose operating system.

Its resource-efficient IPv6 stack covers TCP, UDP, DNS, and RPL, alongside CoAP, LWM2M, and WebSockets. IEEE 802.15.4 and TSCH support sit beneath IPv6, while documented modules also include multicast, secure CoAP, 6TiSCH, and SNMP. MQTT integration is documented as well, including a Linux tutorial that installs Mosquitto and its clients when needed.

Key features

Security and networking

DTLS through Mbed TLS, secure CoAP, and authentication with pre-shared keys or certificates give developers several documented security mechanisms. EDHOC supports mutual authentication, forward secrecy, and identity protection, making it relevant to deployments that need protected device-to-device communication. Link-layer security is supported for IEEE 802.15.4 TSCH, but CSMA link-layer security is planned rather than supported; projects that require CSMA protection should choose a platform that meets that requirement now.

Development and simulation

Cooja native motes and a Renode tutorial provide documented ways to work with simulated devices. The project recommends its Docker image for a consistent development environment and also documents native toolchain installation on Linux and macOS. This gives teams more than one documented development route, though the native toolchain guidance is limited to those desktop systems.

Hardware documentation spans TI cc2538 and SimpleLink, Nordic nRF52840 and nRF5340, Silicon Labs Gecko, OpenMote, Tmote Sky/TelosB, and Zolertia Zoul boards. That breadth is useful when a project can select from those targets; teams committed to other hardware should verify fit before adopting it.

Pricing

Contiki-NG is free: its plan costs nothing and provides an open-source operating system under the 3-clause BSD license, unless a component specifies otherwise. There is no paid tier or free trial to weigh against the core offering, so it suits developers and organizations seeking an open-source embedded OS without a software license fee.

Platforms

Contiki-NG supports Linux, macOS, Windows, and self-hosted use, with deployment at the edge. Documented device families include ARM Cortex-M3/M4, TI MSP430 and CC13xx/CC26xx, and Nordic nRF5340/nRF52840. The operating-system platform options and device support are distinct: check that the specific board and development workflow match the project.

Who it's for

Contiki-NG is a good fit for engineers building low-power IoT devices with limited memory and a need for standard protocols such as IPv6, 6LoWPAN, RPL, CoAP, OMA LwM2M, TSCH/6TiSCH, MQTT, SNMP, or IEEE 802.15.4. Its documented security and simulation options also help teams that need to plan authentication and test networked nodes before deployment. It is a weaker fit when the target hardware is outside its documented platform range or when CSMA link-layer security is mandatory.

Pros and cons

• Pros: A code footprint on the order of 100 kB and configurable memory use as low as 10 kB suit constrained devices.
• Pros: IPv6, application protocols, and IEEE 802.15.4/TSCH support cover a broad range of low-power networking needs.
• Pros: DTLS, secure CoAP, multiple credential options, and EDHOC provide documented security mechanisms.
• Cons: CSMA link-layer security is planned, not currently supported, which rules it out for projects requiring that protection.
• Cons: Hardware support is centered on documented device families, so other targets require careful compatibility checks.

Alternatives

IoT Operating Systems is the category directory for comparing options. Apache Mynewt is another free, open-source embedded OS and development-tools option, with an Apache License 2.0; consider it when that licensing and toolset better fit the project. Particle Device OS may suit deployments that value a managed device plan, but its free tier caps use at 100 devices and 100K Data Operations per month. PX5 RTOS is worth considering when a paid licensing model with full source, perpetual licensing, no royalties, and professional support fits the budget. Micrium OS is another free option. VxWorks may suit a team evaluating a freemium option with up to three online seats. Azure Sphere OS is an alternative for buyers seeking its bundled certified MCU, OS license, and security-service access. PikeOS is a paid alternative, while RT-Thread is another free option.

Verdict

Choose Contiki-NG for low-power IoT nodes when a small configurable memory footprint, broad standard-protocol coverage, and open-source licensing matter most. Its strongest case is constrained edge hardware with a compatible documented target; look elsewhere if your deployment depends on CSMA link-layer security or an unsupported board.