TrackMyGeo

Architecture The app is built as a Next.js web platform with a Node.js runtime and a custom WebSocket server for realtime updates. It uses PostgreSQL and TimescaleDB for relational and time-series data, Azure IoT Hub and Azure Functions for telemetry ingestion, NextAuth with Microsoft Entra External ID / Azure AD B2C for authentication, and Stripe for subscription billing. Tech stack Web app: Next.js, React, TypeScript, Tailwind CSS Server/runtime: Node.js, custom WebSocket server Authentication: NextAuth, Microsoft Entra External ID / Azure AD B2C Data: PostgreSQL, TimescaleDB Device / telemetry: Azure IoT Hub, MQTT, Azure Functions Maps / geospatial: MapLibre GL, TileServer GL Payments: Stripe Infra / cloud: Azure App Service, Azure Bicep State / data fetching: TanStack Query Testing: Vitest, React Testing Library Observability / communications: Azure Application Insights, Log Analytics, Azure Communication Services

200 ok

(That's how pussies launch)

Switch logged in user, is a pain in the auth. Just log auth.

Full stop, end of story.

Geo zone speed events being delivered hours after the event is like being punched in the face, in hospital.

Everyone has a friend that has but never themselves, bought anything worthwhile, off Facebook, Instagram, or Tick Tok. LinkedIn seems the only plausible way forward.

Take off Stripe Sandbox half tested and go for the million subs in an hour, or pretend to be always testing and launch '27.

Added LinkedIn. Laborious.

6. No Single Pane of Glass Fragmented views: multiple accounts, multiple maps, no unified fleet picture. 7. Labor Gap & Update Nightmare Fleet-wide policy isn’t a spreadsheet row — it’s physical labor: firmware, APN, or box settings on dozens of hardwired units means paying someone to crawl under every dash, repeatedly. Same class of pain as only being able to change fleet-wide behavior after a yard day. 8. Calibration Drift & Cheap Hardware Truth Budget boxes: heading / motion sensors drift after months of vibration; you think you have truth, you have slowly wrong truth. Phones aren’t perfect either, but the failure mode here is cheap silicon with no field recalibration without a visit. 9. Cloud vs Landfill Legacy fleets rarely get seamless fleet-wide OTA for brain-in-the-box; units age into unsupported SKUs while phones get app updates from the store and policy updates from the cloud. Their pattern is often capex + crawl + landfill; phone-based stacks are enroll + update + redeploy without a bay lift per VIN. 10. Battery Drain — Whole Fleet “If I put tracking on every phone, do I get fifty ‘my battery died’ tickets?” — ops, HR, and IT worry about support load at scale, not one driver complaining. In practice data packets are usually small and battery impact is often modest (device, settings, and coverage vary). 11. Vehicles Still Need to Be Turned or Moved Regularly Hardwired or poorly designed trackers can flatten batteries if vehicles sit; policy becomes “start every vehicle on a schedule” — another hidden ops tax. Parked fleet = flat lines on the map; tracking doesn’t replace dispatch, maintenance, or rolling stock — you’re not promising magic on cars that never move.

1. SIM & Connectivity Lock-In Global SIMs required, but the providers are impossible to contact. After 2 years, prices jump — you're trapped. 2G networks being switched off globally, bricking older devices. 3G data costs are disproportionately expensive in many regions relative to wages. 2. SMS-Based Tracking Is Broken SMS is unreliable and insecure — other people can see your device. Location is cell-tower-based, so you get an area, not your vehicle's actual position. Device reconfiguration via SMS frequently fails, requiring physical access. APN settings vary by telecom provider and need tech support to change. 3. Dangerous Engine Cut-Off Off-the-shelf devices offer remote engine cut-off via SMS at highway speeds — that's reckless. Cutting into electrical wiring can void fleet insurance and cause fires unless done by a certified mechanic. 4. You Don't Own Your Own Account Resellers register devices under their admin account. When they close shop, you lose access to your own fleet. 10 devices often means 10 separate accounts and 10 separate maps. 5. Hardware That Doesn't Fit Real Life Devices with weak Wi-Fi/GPS chips that "must not be placed near metal" — useless for covert placement under a vehicle. OBD dongles are trivially removed by staff or customers. Many installs require repositioning under the dash with splitter cables — mechanic labour and cost.