How TechnikBrain works.
The short version is up top. If you're an engineer, the detail is one click away — no wall of jargon by default.
From your bike to your phone.
Four stages, and your data stays in storage you own the whole way.
1 · Your tracker
Senses movement and location on the bike, and decides when there's something worth reporting.
2 · Encrypted uplink
Sends location and status over an encrypted connection — cellular, trusted Wi‑Fi, or via your phone.
3 · Your cloud storage
Data lands in cloud storage you own, so it stays under your control.
4 · App & dashboard
You see live and last‑known location, movement alerts, and recent rides.
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.
Technical architecture
For engineers evaluating the platform. This section describes the current direction; the tracker is a prototype in active development, so specifics evolve — we keep this page in step with the build.
Device
Compute
A low-power microcontroller with on-device intelligence (TinyML) that filters motion events and gates the expensive radios — the core battery-saving idea.
Positioning & cellular
A combined satellite-positioning and cellular module provides location and an anywhere uplink. Positioning runs only when a fix is justified.
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.
Secure element
A hardware root of trust holds the device identity key (non-extractable), signs evidence, and verifies firmware updates.
Getting data to the cloud
Cellular
Works anywhere with coverage; highest energy cost. Reserved for events that matter (theft, crash, tamper) and scheduled reports.
Trusted Wi‑Fi
Cheaper when the bike is near a saved network — used opportunistically, batched, and duty-cycled.
Secure phone relay
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.
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
Per-device identity
Each device authenticates with its own credentials; the backend checks ownership before returning any data.
Signed OTA + rollback
Firmware and model updates are cryptographically signed and verified on-device, with rollback protection.
Anti-replay
Reports carry a monotonic counter and timestamp; the ingest path rejects replayed or out-of-order records.
Offline evidence
In dead zones the tracker buffers compact, hash-chained records so tampering is detectable, then uploads later.
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.