Skip to main content

Phimi

Phimi is an independent GPS tracking platform. It starts with four cats wearing Beardpet V53 trackers, but it is designed as a small geospatial IoT platform that can later handle more trackers, users and device types.

The goal is to stop depending on iGPS123: the V53s connect directly to Phimi's Kubernetes cluster over 4G (1NCE SIM, Sunrise network) using JT/T 808-2013 with the vendor's V53 extensions.

BackendRust: Tokio, Axum, SQLx
FrontendNext.js, React, TypeScript (MapLibre in phase 5)
DataPostgreSQL + PostGIS (system of record), MongoDB (raw frame archive, optional)
InfrastructureKubernetes namespace phimi, Argo CD, Harbor
Devices4 × Beardpet V53, firmware TA700_JLT_MP_V1.1 per the vendor example

Where things stand​

  • Done: the JT/T 808 codec with all vendor example frames as tests, the TCP ingest service (registration, authentication, ACKs, sessions, allowlist, metrics), a virtual V53 simulator, the PostGIS schema, the API skeleton, a status dashboard and the Kubernetes deployment.
  • Next: connect the first real V53 (runbook), then persist positions (phase 3).

See the roadmap for all eight phases and the repositories for where the code lives.