Problem

Every device has its own configuration hell

A sensor, a gateway, a control unit, a smart switch — every IoT device needs its network, credentials, endpoints and operating parameters set up. In practice that means writing configuration UI from scratch for every product: a web form, a mobile screen, a serial terminal, or some combination of all three.

The result is that configuration ages differently from firmware. You add a new parameter to the device and have to manually catch up every interface that sets it — the web, the app, the documentation. Over time they drift apart and nobody knows exactly which interface is still telling the truth.

❌ Hand-written configuration

× A new UI for every device, built from scratch again
× A new firmware parameter means touching three different codebases
× The web, the app and the docs drift apart over time
× A configuration error only surfaces in production, at the customer's site

✓ Configuration from a schema

✓ A new device means a new schema, not new code
✓ One interface automatically applies to every device
✓ The firmware and configurator can't drift apart
✓ Parameters are validated before they reach the device

Solution

The schema is the truth. The interface is derived.

Without UNISETUP

With UNISETUP

A developer codes a form for each device

A developer describes the device's parameters with one schema

The configurator is part of that product's firmware

The configurator is a universal runtime over any schema

A new parameter means a new release of the configuration app

A new parameter means a new line in the schema

The same principle ATRUST is built on: the contract is the truth, the interface is just a projection.

Key concept

The SET / WORK switch

Configuration and production mode aren't a software state that could be accidentally flipped remotely — they're two physically separate states of the device. You switch with a pin, a jumper, or a long button press at startup.

SET WORK

SET — the device boots as a configuration access point or exposes a local config endpoint. You connect, configure, disconnect.

WORK — production mode. The configuration interface isn't running, because physically it can't — the pin says the device is doing its job, not waiting to be set up.

Security that can't be bypassed by a software bug — because it isn't in the software, it's in the hardware.

Project status

The first product with no ties to the past

189

entries

Nápad roku (Idea of the Year) 2026 competition — investor visibility preserved

independent
of d.process

the first Atriplex product built with no ties to earlier platforms

hardware
+ software

the concept handles security at the physical pin level, not just in code

UNISETUP grew out of the same experience as d.process: whenever the same work is done by hand for every individual case, sooner or later it falls apart. The difference is the target — d.process addressed business applications, UNISETUP addresses the configuration of physical devices.

Offer

UniSetup R&D Program

Building your own embedded device?
Try UniSetup on up to 5 device types for free.
No license, no commitment.

What you get

✓ UniSetup for R&D
✓ a technical consultation for your first project
✓ the chance to validate your own device
✓ direct feedback from the author

What we need from you

brief feedback,
a short account of your experience,
optionally, consent to an anonymous case study.

Join the R&D program

Contact

Building IoT devices
and configuration is getting out of hand?

Write me a few lines about your hardware and how you handle configuration today. The first consultation is free of charge and takes place online.

jakub@lebeda.eu →

Ing. Jakub Lebeda · Atriplex Algorithmics · Company ID (IČO) 19074671 · +420 607 720 317 · Provodín, Czech Republic