We started by tracking people, not prices.

crewbands: an alarm for the moment nobody is watching

The question came up on a sailing trip: if everyone on board already wears a phone or a fitness tracker, why does a crew still have to notice a person going overboard by eye?

So we built crewbands. It held a live Bluetooth link to every device on board, and the instant one of them left the boat it raised the alarm, froze the last known position, and navigated the helm back to it. It ran an anchor watch through the night. The design decision we cared most about was that it worked with the devices a crew already owned — an ordinary smartwatch or fitness tracker became the sensor, rather than forcing everyone into proprietary hardware.

It was covered in the Austrian startup press, it worked, and it taught us the thing we still build on.

Then came 2020. The pandemic left the boating market becalmed, and in that lull the idea behind tounify took shape. We decided to change focus rather than wait it out.

The same problem, on land

Both companies solve the same shape of problem: a fragmented, unstandardised reality that has to become one reliable signal before anyone can act on it. On a boat that meant a dozen different wearables speaking a dozen dialects, reduced to a single alarm. In European electricity it means every country pricing power its own way — German grid fees split by distribution operator and §14a EnWG status, French regulated TRVE bands, Italian ARERA system charges, Austrian tariffs billed per network level — reduced to a single schema.

And in both cases the data is consequential. A man-overboard position that is approximately right is worthless. So is an electricity price that is approximately right, if someone is dispatching a battery or billing a customer against it. That is why we version every tariff, keep its source, and would rather return an error than a plausible guess.

tounify operates one REST API for static, dynamic, and synthetic electricity tariffs across European markets. Rather than repeat it here, see how the data is sourced and which markets are covered.

tounify never needs your customers. The API is addressed by postal code and tariff identifier — not by person, meter, or account. You can build a household energy product on our data without a single end-user record reaching us, which keeps your GDPR surface where it belongs: with you.

Our infrastructure runs in DigitalOcean's Frankfurt region, data processing in AWS eu-central-1, and product analytics on EU-hosted infrastructure. Web fonts are served from our own servers, so visiting this site sends no data to a third-party CDN. Every processor we use is named in our privacy policy rather than disclosed on request.

tounify holds no ISO 27001 or TISAX certification. We would rather say so plainly than imply otherwise.