Sensor data, turned into decisions. And you own every part of it.

Zero46 is a vendor-neutral IoT consultancy in Malmö. We build connected systems for public organisations and companies, then hand them back: code, data, architecture, all yours.

// the usual mess

A few years in.

Adopt IoT for a while and the estate ends up here. This is normal. It's also fixable.

Every vendor brought a portal.

Sensors, gateways, and platforms from different suppliers, each with its own login and its own export.

The history is hostage.

Years of readings locked in a system you can't leave without losing them.

No single view.

Four teams asking four questions of the same data, in four different tools.

Collected, not usable.

The readings arrive. Joining them up and turning them into a decision is the part nobody sold you.

stack.diff
before ↔ after
// before · typical setup
6 portals · 3 exports · no alerts
// after · one pipeline22:26:27
01 · sensorsMeters & devicesany protocol
02 · bridgeTranslate & normalizeone format
03 · platformStore · route · alertbuilt to scale
21.4°Ctemp
612co₂
42%humidity
live
one platform · one view · live alerts
// 01 — ownership & control

Yours.

Where the code lives, who reaches the data, how you get it all back if we're gone. Decided on day one, in writing.

The code is yours.

One codebase, in your repository. No black boxes, no escrow to invoke.

The data is yours.

Your storage, your keys, your retention. History survives a vendor change, including ours.

The architecture is yours.

Documented decisions in plain language. Defensible three years in.

Replaceable on purpose.

When we hand over, you can run it, or hand it to anyone else.

Deploy where you want.

On-prem, Swedish sovereign cloud, EU, or US hyperscaler. No quota, no quiet alignment.

Built for the regulation.

NIS2, DORA, and the CRA. Operational data is in scope, and we build for it.

// 02 — services

What we do.
And what we don't.

No reselling, no licences. We build and run connected systems with your team. Most projects touch two or three of these.

01flagship

IoT architecture & strategy

The right stack for the next five years, not the next demo.

strategyreviewroadmap
02deep-dive

Sensors & edge integration

Data off the device and onto the network, reliably, even when the signal drops.

MQTTModbuswM-Bus
03core

Data platform

Time-series storage, event routing, and clean APIs. Built to scale.

PostgresTimescaleAWS
04core

Run & operate

Dashboards, alerts, and on-call. We run it with you, then hand over.

Grafanarunbooks
05craft

Portals & dashboards

The screens your team opens every morning. Role-based and focused.

ReactVueTailwind
// 03 — where to start

Start where you are.

Each one is fixed-scope, with a named output and a named end.

Entry

NIS2 workshop

1 day

Where your operational data stands against NIS2. Leave with a prioritised list.

Architecture second opinion

1 week

About to commit to a platform or vendor? We review it before you sign, and give you a written verdict.

Diagnostic

IoT Platform Readiness Assessment (NIS2)

A structured review of your estate against NIS2 and your own goals. Defines the next step in writing.

Discovery / förstudie

2 weeks

A look at what you have, the real problem, and a plan with a number on it.

Pre-procurement

Kravspec-stöd (LOU)

Shape the requirements before you tender, so you buy what you actually need.

Recurring

Fractional IoT architect

monthly

A senior architect on retainer: design reviews, vendor calls, roadmap. Without a full headcount.

Not sure which fits? A 30-minute call sorts it. Book one here.

// the deadline that's already here

NIS2 is in force. Sensor data is in scope.

Operational and sensor data sit squarely inside NIS2, and most IoT estates were never built for it. We design for it from the architecture stage, not patch it in afterwards.

  • In force since January 2026
  • Every kommun and region in scope
  • Accountability reaches named individuals
// 04 — industries

Where the work has been.

Eight years across these sectors. The public-sector platform is Zero46's; the rest is the track record behind it.

// case pattern · public-sector

One platform. Every team.

We're building a sensor platform for a Swedish municipality. One system, many teams: indoor climate, alarms, air quality, energy. Same data, different questions.

teams
4
protocols
6+
status
live
// 05 — process

Four stages.

Every project runs the same way. Each stage has a clear output, a set price, and a named end.

01 /
Discover
We look at what you have, find the real problem, and come back with a plan and a number.
2 wkfixed fee
02 /
Design
The architecture, the data model, the picks. Decisions you can defend three years in.
3–5 wk
03 /
Build
We build it with your team, not next to them. One codebase, clear ownership, no handoffs.
8–20 wk
04 /
Operate
We run it with you, then hand it over on a date we set up front.
ongoing
// 06 — a word from the founder

From my desk to yours.

Zero46 is a small IoT consulting practice based in Malmö. Here's the short version from the person running it.

Poya Shad, founder of Zero46
founder · engineer · malmö

Eight years of shipping meter fleets, alarm systems, and data platforms shaped how Zero46 works. One senior architect, not an account team. The person you meet is the person who builds it, and stays on the project from first call to handover. You won't talk to a salesperson, and you won't be passed to whoever happens to be free.

If it needs to survive production, I'd like to hear about it.

— PoyaPoya Shad
nowSwedish municipality · city-sensor platform
——Axians · industrial data engineering
——PRYM.io · edge + cloud
——Careium · elder-care alarms, Sweden-wide
——Waltero · smart-meter fleets
// 07 — faq

First questions.

Short answers. Ask if yours isn't here.

We work in four named stages: Discover, Design, Build, Operate. Each has a clear output, a set price, and a named end. Most projects run 3 to 9 months end to end.
No. Our advice isn't tied to a vendor quota. If you're on AWS, Azure, or on-prem already, we work inside it.
Fixed price per stage, scoped on the first call. Each chunk has a set number before it starts, so no surprise invoices.
One senior architect, hands-on. You won't talk to a salesperson, and you won't be reassigned to whoever happens to be free mid-project. Behind it: eight years of production IoT, including smart-meter fleets at Waltero, alarm systems at Careium, and industrial data work via Axians and PRYM.io, now running a sensor platform for a Swedish municipality. The person on your first call is the person writing the code.
Based in Malmö, Sweden. We work across the EU and UK, on-site when it helps, remote when it doesn't.
You keep the code, the documentation, and the know-how. We offer light support afterwards if you want it.
// 08 — start

30 min first.
Two hours if it fits.

Book a 30-minute call and tell us what you're building. If it fits, we follow with a two-hour working session: architecture sketch, honest scope, no invoice.

// based inMalmö, SE
// reachEU + UK
// languagesEnglish · Svenska