Technology

How TechnikBrain works.

A small tracker on your bike, an encrypted link, cloud storage you own, and an app that tells you what changed. The simple picture comes first — engineers, keep scrolling for what's under the hood.

Follow the data Under the hood
  • Sleeps until something changes
  • Encrypted in transit
  • Stored in your own cloud storage
Illustration: a tracker on the bike's top tube sends an encrypted signal up to cloud storage the owner controls, and the owner's phone shows the bike on a map. Your storage Tracker Your phone
The simple version

From your bike to your phone.

Four stages, and your data stays in storage you own the whole way.

  1. 1

    Your tracker

    Senses movement and location on the bike, and decides when there's something worth reporting.

  2. 2

    Encrypted uplink

    Sends location and status over an encrypted connection — cellular, trusted Wi‑Fi, or via your phone.

  3. 3

    Your cloud storage

    Data lands in cloud storage you own, so it stays under your control.

  4. 4

    App & dashboard

    You see live and last‑known location, movement alerts, and recent rides.

Battery life

Why it lasts on a small battery.

Instead of streaming constantly, the tracker does light on‑device analysis to decide when a location fix or an upload is actually worth the energy. Most of the time it sleeps — it wakes when something changes.

  • Asleep by default

    An always-on, ultra-low-power motion sensor keeps watch while the rest of the tracker sleeps.

  • Movement wakes it

    Light on-device analysis filters motion events before any radio is switched on.

  • Radios only when it's worth it

    A location fix or an upload happens when it's justified — then straight back to sleep.

A day in the life of the tracker
Power use over a day Power stays at a low sleep level most of the day. A bump in the bike rack causes a tiny blip that the tracker analyses and ignores. Real movement wakes it for a location fix and a short upload, after which it drops straight back to sleep. 06:00 12:00 18:00 Power Time of day → 1 2 3 4
  1. 1Asleep — the motion sensor keeps watch.
  2. 2A bump in the rack — analysed, no radio used.
  3. 3Real movement — a location fix.
  4. 4A short upload, then back to sleep.
Under the hood

The technical architecture.

For engineers evaluating the platform. This describes the current direction; the tracker is a prototype in active development, so specifics evolve — we keep this page in step with the build.

Illustrated circuit board of the tracker: 1 the low-power microcontroller in the middle, 2 the positioning and cellular module, 3 the motion sensor, 4 the secure element, with the battery alongside. MCU TinyML Battery 1 2 3 4

Inside the tracker

Four parts do the work; the rest of the board is power and plumbing.

  1. 1

    Compute

    A low-power microcontroller with on-device intelligence (TinyML) that filters motion events and gates the expensive radios — the core battery-saving idea.

  2. 2

    Positioning & cellular

    A combined satellite-positioning and cellular module provides location and an anywhere uplink. Positioning runs only when a fix is justified.

  3. 3

    Motion sensing

    An inertial sensor with an always-on, ultra-low-power motion filter is the primary wake source, so the main processor can sleep.

  4. 4

    Secure element

    A hardware root of trust holds the device identity key (non-extractable), signs evidence, and verifies firmware updates.

Three ways the tracker's data reaches your storage: 1 cellular through a cell tower, 2 a trusted Wi-Fi network, 3 your phone over Bluetooth. Number 4 marks the tracker's policy engine, which picks the lowest-energy path that fits. 4 Tracker 1 2 3 Your storage

Getting data to the cloud

Three routes, one rule: use the cheapest path that still gets the job done.

  1. 1

    Cellular Most energy

    Works anywhere with coverage; highest energy cost. Reserved for events that matter (theft, crash, tamper) and scheduled reports.

  2. 2

    Trusted Wi‑Fi Less energy

    Cheaper when the bike is near a saved network — used opportunistically, batched, and duty-cycled.

  3. 3

    Secure phone relay Least energy

    When your phone is nearby, the tracker can hand an encrypted bundle to the app to forward — lowest tracker energy. The phone is an opaque courier; the payload is encrypted for the cloud.

  4. 4

    Cost-aware choice

    An upload policy engine picks the lowest-energy path that meets the required confidence. Emergency events always use cellular where possible.

Security model

Trust, built in layers.

Each layer answers a different way things go wrong: a cloned device, a tampered update, a replayed report, a gap in coverage.

  • Per-device identityEach device authenticates with its own credentials; the backend checks ownership before returning any data.
  • Signed OTA + rollbackFirmware and model updates are cryptographically signed and verified on-device, with rollback protection.
  • Anti-replayReports carry a monotonic counter and timestamp; the ingest path rejects replayed or out-of-order records.
  • Offline evidenceIn dead zones the tracker buffers compact, hash-chained records so tampering is detectable, then uploads later.
Layers of protection around the tracker's own identity: signed firmware, a report counter against replays, and hash-chained records. Below, four numbered reports linked into a chain. #1041 #1042 #1043 #1044

Data is encrypted in transit and stored in cloud storage the account owner controls. The platform processes telemetry to route it into that storage and to power alerts — it is not hidden from the server, but it stays in the owner's account.

Questions about the platform?

Happy to go deeper with engineers, clubs and fleet operators evaluating the pilot.

Get in touch