OBJEX LABS
LUMA
Smart lighting controller
ELPM-S3LW
Extreme low-power module
Your space. Your hardware. Your data.
Somewhere along the way, buying something stopped meaning you owned it.
Our generation has watched this become the standard. Music became a monthly subscription. Then movies, software, books. One category at a time, access replaced ownership.
We believe this shouldn't become the model for the smart objects that are part of the spaces where we live and work.
To us, technology should give people back control, not turn every object into a service.
What that means in practice
A device you buy from us works without our servers. You don't need an account to use hardware you paid for. The cloud is something you add, not something you accept. Your data is yours. Documentation and support are part of the product, not a favour. And if OBJEX LABS disappeared tomorrow, the lights would still come on.
Two things reach us, and you decide about both. Firmware updates come over the network from our servers. Diagnostics like temperature, uptime and error counts help us find problems before you do, and you can switch them off whenever you want.
Once it's yours, it owes us nothing.
LUMA is the first product we built on that principle. A lighting controller that runs locally from the first boot, with no proprietary app and no mandatory account.
It speaks open protocols. Connect it to Home Assistant, to your own scripts, to whatever you already run. Or to nothing. Anything that leaves your network leaves because you decided it should. Connectivity is never a requirement. It is always your choice.
Privacy and security
A building collects more data about you than any phone: when you come home, which room you're in, when you sleep. Today that data almost always ends up on someone else's servers. We're building the alternative, one device at a time.
A dimmer looks harmless. But knowing when a light comes on means knowing when someone got home, which room they're in, and what time they stopped working. If that information never leaves the device, there is nothing to leak. That's why LUMA processes everything locally: not as an architectural preference, but because the surest way to protect data is not to hold it.
What does stay is protected where it sits. Every device carries a hardware secure element that holds the cryptographic keys: not in the firmware, not in memory, not recoverable by dumping the flash. Firmware is signed, and the device refuses what it doesn't recognise.
The best privacy is the data you never collected.
Zero outsourcing
We couldn't claim a device is secure if we hadn't written its firmware. We couldn't say a board is well built if we had never seen it assembled.
We design the boards, write the firmware, and assemble the products on our own line in Palermo. Not because it's cheaper (it isn't) but because it's the only way we can answer for what we sell.
Where this goes
We don't want your space to adapt to our products. We want products that adapt to your space. Lighting is the beginning. Then sensing, control. What we build changes. Who it answers to doesn't.
You control your space. Nobody else.
Inside the lab · On commission
For other companies we design and build hardware and software. The same line that assembles LUMA and the ELPM modules runs boards that are not ours, from the first schematic to the assembled product, and the code that runs on them is ours too, from the firmware to the applications that talk to the device.
Consulting
Requirements, architecture, part selection.
Hardware
Schematic, PCB layout, prototype and tests on the bench.
Software
Firmware, applications and the interfaces that talk to the device.
Production
Assembly and inspection on our line in Palermo.
