Sovereign IoT Platforms

From Sensor To Decision

Zero46 builds sensor data platforms for water, energy, and city operations. The platforms are vendor-neutral and NIS2-ready. We build them, then your team owns them.

55.605° N · 13.003° EWater · Energy · Cities
01 · The Problem

Why connected infrastructure stalls.

The pattern is the same in water, energy, buildings, and city streets. Each device sends data. The estate still cannot answer a simple question.

We connect everything to one pipeline, from device to decision. The same architecture works in every industry.

The estate todayOne pipeline · yours
Siemens SCADAKamstrup portalwM-Bus v1.2!LoRaWAN gatewaycsv · email exportsPDF · manual entry!BRIDGETranslate & normalizePLATFORMStore · route · alertdocumented · yoursDashboardsone viewAlertslive · routedDecisionsbacked by data
Every vendor brings a portal.

Six suppliers means six logins, six formats, and six exports. The data exists, but no system collects it in one place.

You rent the platform.

The vendor owns the data model, the integrations, and the history. An exit costs more than another year of fees.

The regulation is in force.

NIS2 puts connected infrastructure in scope. An estate that is spread across portals and spreadsheets cannot show compliance.

02 · Ownership

You own everything we build.

We decide three things on day one, in writing: who owns the code, who reads the data, and how you get everything back.

The code is yours.

You get one codebase in your repository. Nothing is hidden.

The data is yours.

The data stays in your storage, with your keys and your retention rules.

The architecture is yours.

We document each decision in plain language.

Replaceable on purpose.

Operate it yourself, or give it to another supplier.

Deploy where you want.

On-premises, in a sovereign cloud, in the EU, or on a hyperscaler.

Built for the regulation.

The design includes NIS2, DORA, and CRA from day one.

How we build platforms
03 · Services

What we build.

We do not resell, and we do not sell licenses. We design, connect, and operate sensor platforms with your team. Then we give the platform to you. Most projects use two or three of these services.

01

IoT architecture & strategy

We select the stack for the next five years.

What you get
  • Target architecture and data model
  • Vendor and platform review
  • Documented decision log
  • A costed roadmap
Good fit when

you must soon commit to a platform, or you inherited one that you do not trust.

02

Sensors & edge integration

We move data from the device to the network, from LoRaWAN to wired lines. The pipeline continues when the signal drops.

What you get
  • LoRaWAN networks, gateways, and provisioning
  • Protocol integration across mixed hardware
  • Normalization to one format
  • Store-and-forward for dropouts
Good fit when

the readings come from mixed hardware and arrive late, incomplete, or not at all.

03

Data platform

We build time-series storage, event routing, and clean APIs. The platform scales with your estate.

What you get
  • Time-series storage that scales
  • Event routing and rules
  • Documented, versioned APIs
  • Retention and access controls
Good fit when

your data sits in six portals and needs one source of truth.

04

Run & operate

We operate the dashboards, the alerts, and the on-call with you. Then we give the operation to your team.

What you get
  • Dashboards and alerting
  • On-call and runbooks
  • SLOs and incident response
  • A handover plan with a date
Good fit when

the platform is in production, and your team must own the uptime.

05

Portals & dashboards

We build the screens that your team opens every morning. Each role gets its own view.

What you get
  • Role-based portals
  • Operational dashboards
  • Reports and exports
  • Accessible, responsive UI
Good fit when

different teams need different views of the same data.

No reselling.

We get no commission from AWS, Azure, or any vendor. Our advice is not connected to sales.

No lock-in.

There is no proprietary runtime, no private protocol, and no embedded license. You can leave with everything.

No black boxes.

We document the code, the data, the history, and the architecture. They are yours from day one.

No forever-engagement.

Every project has a handover date from the start. We leave when your team is ready.

We build inside the stack that you have, or we design the stack that you do not have. You own the result either way.

AWS · Azure · Grafana · ThingsBoard · Node-RED · InfluxDB · Timescale · PostgreSQL · MQTT · or from scratch

05 · Regulation

NIS2 is in force. Your IoT estate is in scope.

We design and build platforms that can show compliance. This includes architecture, data ownership, vendor dependencies, isolation, observability, and security posture. We document everything from day one.

06 · How we work

Start where you are.

Every engagement has a clear output, a set price, and a named end. A full build runs through Discover, Design, Build, and Operate in 3 to 9 months.

Entry

Architecture review

1 week

If you must soon commit to a platform or vendor, we review it before you sign. You get a written verdict.

About architecture review
Diagnostic

Discovery

2 weeks

We examine what you have, find the real problem, and give you a plan with a number on it.

Pre-procurement

Procurement requirements support

We shape the requirements before you tender, so you buy what you need. This works under Swedish LOU or any EU procurement framework.

About procurement requirements support
Recurring

Fractional IoT architect

monthly

A senior architect on retainer for design reviews, vendor calls, and roadmap work, without a full headcount.

// the full build

The complete platform, built with your team.

One engagement covers the whole path, from the first interview to a platform in production. Each stage has a fixed scope and a fixed price. The code goes into your repository from the first sprint, and the handover date is set before we start.

3 to 9 months
fixed price per stage
handover date set up front
01
Discover

We map your estate and decide together what to build.

02
Design

Architecture and data model, documented and owned by you.

03
Build

Built with your team, in one codebase, in your repo.

04
Operate

Run together, then handed over on the set date.

07 · Contact

Book a first call.

Tell us where you stand in a 30-minute call. If there is a basis for an engagement, we come back with a proposal for scope and setup.

08 · About

Small by design.

Zero46 is a small firm of senior people in Malmö, Sweden. You work with the architect directly, with no handoffs and no account team.

For eight years we built meter fleets, alarm systems, and data platforms. This experience shaped how Zero46 works. The architect who scopes your project also builds it. When a project needs more people, a specialist network helps. The architect stays.

We also work on the buyer side: Zero46 writes the security and NIS2 requirements for public procurement documents.

If it must survive production, we want to hear about it.

Track record
  • nowSwedish municipality · platform architecture
  • · ·Axians · industrial data engineering
  • · ·PRYM.io · edge + cloud
  • · ·Careium · elder-care alarms, Sweden-wide
  • · ·Waltero · smart-meter fleets