For installation companies

Stop paying to build software that already exists

You fit the meters. We provide the platform your customer looks at.

Your own remote-reading portal is months of development and maintenance that never ends. Datakubo hands it to you finished, under your brand, connected to the meters you have already fitted — whatever brand they are — and running this afternoon.

No card. You keep your gateway, your operator and your network server. If you do not see data in 30 minutes, we set it up for you and give you 3 months free.

From webhook to first reading on screen
30 min
From webhook to first reading on screen
Meters run by a single installer in Tarragona
150+
Meters run by a single installer in Tarragona
Of development: you write no code
€0
Of development: you write no code

This is what you open every morning

The dashboard you run every community from: each customer, each meter and each alarm in one place. Your customer logs into something else entirely — their own consumption, in the portal under your brand.

Click the sidebar to move through the product.

portal.yourbrand.com/analytics

Platform

Operations

Insights

Admin

Analytics

Where the water nobody is looking for goes

Torre Gassià communityZone 2Last 30 days

Main meter against the sum of the individual ones

The gap between the bar and the line is water that reaches no meter at all

Main:1,412 m³Sum of individuals:1,346 m³Unmetered:66 m³

Where are those 66 m³?

  • Expected baseline use12 m³
  • Meters offline8 m³
  • Unexplained46 m³

This is the calculation that turned a community in Tarragona into a case study: unmetered water nobody was looking for.

Two ways it pays for itself

The first is what you stop spending. The second is what you start billing. Most installers arrive for the second and stay for the first.

What you save

You neither build nor maintain software

A multi-tenant portal with history, permissions, alerts and a zone hierarchy is not two weeks of work: it is months of development and, above all, maintenance that never ends. Every new meter, every odd payload and every LNS update becomes your problem again.

  • No development: you hire nobody and you do not become a software company
  • No maintenance: decoders, uptime and backups are ours
  • No on-call: you are not the one getting up if the portal falls over on a Sunday
  • No migrations: change gateway or operator and your customer’s portal never notices

What you earn

The installation bills once; the portal bills every month

It is the same fleet of meters you already fitted, billed differently. You set the fee, you issue the invoice and the customer relationship stays yours: Datakubo bills you, never them.

  • You move from billing an installation to billing a monitoring service
  • You set the price, based on your area and what you include
  • You spot the leak before your customer does and close the repair yourself
  • A customer with a portal switches supplier far less often

Run it with your own numbers

Put in the meters you already have connected and what you would charge for each per month. The €2 starting point is an example to get you moving the figure, not a recommended price.

You set the price. The €2 starting point is only an example to get you moving the figure — not a recommended price, and not a market rate.

Revenue per month
€500
Revenue per year
€6,000
Revenue per meter per year
€24.00

With 250 meters at €2.00 a month you bill €500 a month, €6,000 a year.

This is what you bill, before costs. What the platform costs you — a fixed monthly fee with meters included, plus a price per additional meter — we give you in full on the demo call; you can see it on pricing. It also excludes meters, gateways, connectivity and your own labour.

What not having it actually costs

It is not the price of a platform. It is the conversation that repeats on every installation and was never in the quote.

  1. The meters are already in

    You have swapped or adapted the meters in the building, the irrigation community or the hotel. The field work is done and paid for.

  2. The data flows and then stops

    Every meter sends its readings over radio. The frames reach your network server and sit in a console you cannot show anyone.

  3. The customer asks where to look

    And the LNS does not answer that: its interface is built for a network engineer, not for the head of a residents’ association.

  4. You improvise with spreadsheets

    You export a CSV each month, tidy it up and email it. That works with two customers. With ten it eats your evenings.

  5. You consider building it

    And that is where the margin goes: months of development, open-ended maintenance and the responsibility of keeping it standing every night.

  6. Meanwhile you are not selling the service

    No portal means no monthly fee to charge. Every month that passes is recurring revenue you are not billing on meters that are already installed.

Datakubo hooks in at the end of that chain, by webhook, and handles the one thing your LNS does not: showing it to your customer.

The vendor trap: software that only reads their meters

It is the most common pattern in the sector. You buy meters from a manufacturer and they offer you their platform "free", or nearly. The small print is that the platform only understands their meters.

The day you want to change brand — on price, on lead time, or because the customer already has something else fitted — you find that changing meter means changing software, and changing software means moving every one of your customers to a new portal.

  • Your hardware supplier stops being a technical decision and becomes one you cannot walk away from
  • You negotiate meter prices from a far weaker position
  • A mixed fleet — normal once you have a few years behind you — ends up spread across two or three platforms
  • If the manufacturer raises prices or discontinues a model, the problem is yours

Datakubo does not sell meters. Any water meter that reports on its own works, and payloads are normalised on the way in, so meters from different manufacturers appear in the same view with the same charts and the same alert rules. If you have a payload we do not support, we write the decoder free within 24 hours.

Your customer never sees the name Datakubo

Switch brand in the selector and look at what your customer sees when they log in. Same product: the only thing that changes is whose it is.

Pick an example brand

aqualinks.datakubo.com
AquaLinksMeter 12 · Unit 3B

My water consumption

This month

14.2 m³

−8% vs last month

Last 7 days

No alerts on your meter
Portal by AquaLinks24/7

Your customer sees your brand. The name Datakubo appears nowhere.

You upload your logo, pick your colour and your customers log in at your subdomain. We bill you; what you charge your customer is your decision and your invoice.

How it connects to what you already have

The integration is an HTTP forward. Your network server already receives the decoded uplink; you just tell it to send it to Datakubo as well, with your API key in the header.

We do not replace your LNS. ChirpStack, The Things Network or whichever server your gateway ships with keep managing the network, the keys and device provisioning.

    1. MeterThe one you already fitted
    2. LoRaWAN / NB-IoTYour radio or your SIM
    3. TTN / ChirpStack / APIYour network server
    1. DatakuboInbound webhook
    2. Your brandYour logo, your subdomain
    3. Your customerTheir own login

Datakubo joins at the end of the chain. Change gateway or operator tomorrow and it is the network layer that changes, not your customer’s portal.

With NB-IoT you do not even need a gateway

NB-IoT meters carry their own SIM and send straight to Datakubo’s HTTP endpoint over the cellular network. No gateway and no network server in between.

It is the sensible option when the points are scattered — plots, wells, isolated homes — and a LoRaWAN gateway would cover two or three meters.

    1. NB-IoT meterWith its own SIM
    2. Cellular networkNo gateway
    3. DatakuboHTTP endpoint
    4. Your customerTheir own login

Real catches

What the platform flagged on its own, before the bill did.

Zone leak · found on its own

66,000 litres that reached no meter

In August, the zone balance on a community in Tarragona uncovered unmetered water nobody was looking for. The platform opened the alarm and named the zone without anyone reading the chart.

Consumption anomaly · 6 nights

A meter running steadily through the night

Six nights in a row above its own 30-day history. Not a generic threshold: that meter compared against itself.

Hardware alarm · on the spot

Low battery before it went silent

The meter reported it itself and the alarm reached the portal on the same uplink. It gets swapped on the next scheduled visit, not on an emergency call-out.

Device down · 48 h

A meter that stopped reporting

Flagged on its own after 48 hours, with no rule to configure. The difference between you finding out and your customer telling you.

Read the full AquaLinks case study

The situations Datakubo is used in most. Each page goes into the detail of that case without repeating this one.

What it costs

A fixed monthly fee with meters included, plus a price per additional meter. No setup fee and no lock-in: if it does not fit, you cancel.

  • Starter plan from €49/month, with meters included
  • White label, alarms and the customer portal included from the first plan
  • What you charge your customer is your decision, and your invoice
  • No per-user cost: add as many residents as you need
See plans and pricing

We carry the risk

Two written guarantees, so setting it up does not cost you an evening

We are not asking you to spend your evenings fighting a payload. If something does not work, we fix it and it costs you nothing.

30 minutes

30-minute setup guarantee

If you cannot register the webhook and see decoded data on your first customer within 30 minutes, we set the account up for you on a call and give you the first 3 months free.

24 hours

24-hour decoder guarantee

Got a water meter with an odd or unsupported payload? Send us the datasheet and we write the decoder free within 24 hours.

Both guarantees apply from day one and on any plan. No small print.

Join the network and we pass you the projects that reach us

Property managers and communities reach Datakubo wanting remote reading with no installer in their area. Those projects go to the installers in the network.

  • Projects from administrators and communities with no installer in their area
  • You run them from your own dashboard, under your brand
  • The customer is yours — we stay out of that relationship
Join the installer network

Installer network available in Spain only.

Mechanical meters, or none fitted? We put an installer on it.

The platform needs meters that report. If yours are read by hand, or the property has nothing fitted yet, we put you in touch with an installer from our network: they coordinate the installation or the swap and hand the meters over already sending data to your dashboard.

  • Installation or swap coordinated, no crew of your own
  • Meters handed over already paired and reporting
  • You stay the customer's provider — the relationship is yours
Request installation for your property

Installer network available in Spain only.

Installer questions

Do I need to change my meters?

No. If the meter already sends readings on its own, it connects as is. Datakubo never touches the field equipment: it receives the frame already decoded by your network server.

Does it work with meters from several brands at once?

Yes, and that is the normal case. Payloads are normalised on the way in, so meters from different manufacturers appear in the same view with the same charts and the same alert rules. We do not sell meters, so we have no interest in tying you to a brand.

Does it work with LoRaWAN?

Yes, that is the most common case. Your LoRaWAN network server forwards the uplink to Datakubo over HTTP and the meter appears in the dashboard.

Does it work with NB-IoT?

Yes. With NB-IoT there is no gateway or LNS in between: the meter sends straight to Datakubo’s HTTP endpoint over the cellular network. It is the sensible option on scattered installations where a LoRaWAN gateway would cover two or three meters.

Can I use ChirpStack?

Yes. You add an HTTP integration in your ChirpStack application pointing at Datakubo’s ingest endpoint, with your API key in the header. ChirpStack v4 and v3.

Does Datakubo replace my LNS?

No, and it is not meant to. Your LNS keeps managing the network, the keys and the devices. Datakubo is the business layer on top: what your customer sees.

Do I need to change my infrastructure?

No. You keep your gateways, your operator and your network server. The integration is an HTTP forward from where the frames already arrive.

What if I have a payload you do not support?

Send us the meter datasheet and we write the decoder free within 24 hours. It is one of the two written guarantees.

Can each community have its own login?

Yes. Each community is an isolated customer inside your account, with its own meters, zones and users. One community’s data is never visible from another.

Can I use my own brand?

Yes. You upload your logo, pick your brand colour and your customers log in at your subdomain (yourbrand.datakubo.com). A custom domain such as portal.yourbrand.com is announced on the Pro plan and is not available yet.

Can I charge my customers a monthly fee?

Yes. Datakubo bills you for the platform; what you charge your customer is your decision and your invoice. Datakubo never bills your customers or issues receipts in your name.

How long until the first customer is running?

Under 30 minutes from adding the HTTP forward on your network server to seeing decoded data. If you do not get there, we set it up for you and give you 3 months free.

Written by

Xavier Mor Founder & CTO, DataKubo

Builds DataKubo working directly with LoRaWAN and NB-IoT water meter installers in Spain, taking their field readings into a branded portal for each of their customers.

You install the metering. We provide the software.

Connect a meter you already have transmitting and see how your customer’s portal looks. If it does not fit, you cancel and you have paid nothing.