Update every device in the field. Without bricking one.
Atomic A/B updates, delta images and staged rollouts for Yocto, Buildroot and Debian fleets. Signed end to end, rolled back automatically.
Helps support EU Cyber Resilience Act (CRA) compliance efforts with signed artifacts, audit logs, and controlled rollouts.
$ nulix release create core-image-2.4.1.wic.bz2 ✓ signed with ed25519 key ✓ delta built against 2.4.0 $ nulix rollout start --group canary --percent 5 ✓ pushing to canary... ! health check failed on gw-0417 ✓ auto-rollback to last good slot · paused
Everything between your build server and the device
One platform for artifacts, signing, rollout and monitoring. Need help with hardware, firmware, or embedded Linux? See our services.
A/B updates with auto rollback
Fail safely: write to inactive slot, verify health, auto-rollback on boot failure.
slot A ↔ slot B · health check → commit/rollback
Delta + resumable downloads
Send only diffs. Resume after drops for slow LTE or flaky links.
$ curl -I ... · range requests · partial reassembly
Staged rollouts with control
Canary, % or tags. Pause/abort on error thresholds in one click.
canary → 10% → 100% · pause on failure
Integrate into your toolchain
Yocto layer, Buildroot package, Debian package, CLI + REST API for CI.
INHERIT += nulix · signed in CI · artifacts versioned
From commit to fleet in three steps
Add the agent
Include the NULIX client in your image through your layer or package. Devices enroll on first boot.
Push a release from CI
Upload the build artifact. It is signed, versioned and diffed against previous releases.
Roll out and monitor
Start with a canary group, watch health signals, then widen to the whole fleet.
Security you can show an auditor
A repeatable, documented path for shipping security patches across the product lifetime.
Copy a config and ship in minutes
Drop NULIX into your Yocto build with a couple of lines. No custom server code required.
# Enable NULIX OTA
INHERIT += "nulix"
NULIX_SERVER = "https://ota.nulix.example"
NULIX_SIGNING_KEY = "${TOPDIR}/keys/nulix-ed25519.pem"
NULIX_FLEET = "gateway-prod"BBLAYERS ?= " \ /path/to/poky/meta \ /path/to/poky/meta-poky \ /path/to/meta-openembedded/meta-oe \ /path/to/meta-nulix \ "
curl -sSL https://get.nulix.example | sh
Simple, predictable pricing
Start free. Scale as you ship.
Free
For evaluation and small fleets
- ✓Up to 25 devices
- ✓A/B updates & rollback
- ✓Signed artifacts
- ✓Community support
Growth
Most popularFor teams rolling to production
- ✓Up to 1,000 devices
- ✓Delta updates & resumable downloads
- ✓Staged rollouts & groups
- ✓Fleet observability
- ✓Email support
Enterprise / Self-hosted
For scale, compliance, or air-gapped
- ✓Unlimited devices
- ✓Self-hosted or private cloud
- ✓Air-gapped deployments
- ✓RBAC & audit logs
- ✓SLA & dedicated support
NULIX vs the alternatives
Embedded teams usually weigh Mender, RAUC with hawkBit, SWUpdate, or building their own.
| Feature | NULIX | Mender | RAUC + hawkBit | SWUpdate | DIY |
|---|---|---|---|---|---|
| Atomic A/B + auto rollback | ✓ | ✓ | ✓ | ~ | Build yourself |
| Delta & resumable | ✓ | Add-on/varies | Limited | Limited | Complex |
| Staged rollouts / canary | ✓ | ✓ | Possible | Manual | Complex |
| Yocto/Buildroot/Debian packages/layer | ✓ | ✓ | Partial | ✓ | N/A |
| Fleet dashboard | ✓ | ✓ | Basic | None/minimal | Build yourself |
| Self-hosted / air-gapped | ✓ | Enterprise | ✓ | ✓ | ✓ |
| Time to first rollout | Minutes | Hours–days | Days–weeks | Days | Weeks–months |
Comparison is based on common capabilities; check vendor docs for specifics.
Request a demo or start free
Tell us a bit about your fleet and we’ll get you set up.
What happens next
We’ll review your request and share a test environment + onboarding checklist.
FAQ
Answers for embedded teams.
Do you support offline or disconnected devices?
Yes. Devices can download when connectivity returns; updates are resumable and staged. For fully air-gapped fleets, NULIX can be self-hosted with no outbound dependency.
How are bandwidth limits handled?
Delta updates minimize transfer size. Rollouts are rate-limited per group and downloads are resumable, so they play nicely with metered LTE and constrained links.
What is the rollback behavior?
A/B slots with health checks. If the new slot fails to boot or health checks fail, the device automatically boots back to the last known good slot and reports the rollback to the fleet dashboard.
Where is data stored / data location?
With the managed service, artifacts and metadata are stored in your selected region. For self-hosted deployments, all data stays in your infrastructure with no device data sent to NULIX.
Can I self-host NULIX platform?
Yes. The Enterprise/Self-hosted tier supports on-prem and air-gapped installations with the same signing, rollout, and observability features.
Ship your next update with confidence
Connect a test device in minutes and run your first rollout today.