We change device behavior with JSON. Not firmware.

We simplified device behavior into two primitives:

Button

Switch

That’s it.

Then we define what they do in JSON.

Not as configuration, but as actual execution logic.

Instead of:

rewriting firmware

rebuilding

reflashing

We just change JSON.

We built this on top of the Matter standard.

So it’s not a simulation.

It runs on real devices.

Here’s what that looks like:

{

"trigger": "button",

"action": "start",

"limit": "5min"

}

Same hardware.

Different behavior.

When we pushed this approach,

we started getting structures like this:

{

"Label": "Keep Warm",

"PinNo": 21,

"FixedLabel": [

{ "Label": "limit", "Value": "max-30min" },

{ "Label": "warning", "Value": "thermal-risk" }

],

"MaxSec": 1800,

"NotOnPin": [22]

}

Behavior, constraints, and limits are all defined together.

You don’t even need to write JSON — answer a few questions and it generates it.

This is not just an idea.

We built a working system where this runs:

👉 https://anna.software/

And here’s how it connects to real devices:

👉 https://github.com/anna-soft/Nemo-Anna

We’re preparing for a Product Hunt launch.

Before we do:

Would you actually use this?

What would stop you?

Where does this approach fail?