01 · The context
Business fleets lose on average 23% of their efficiency due to lack of real-time visibility. Dispatchers are still working on updated Excel sheets every hour. Alerts arrive when the damage is already done.
You're born to overturn this. Not a tracking app, but an operating system for the fleet: predictive AI, CAN-Bus telemetry, scalable enterprise design system.
This is the first time I've seen this.
The map is not just a tracker. It's the visual operating center of the fleet: real-time AI clusters, slide-over panels with vehicle history, predictive routing.
Every dot on the map is a WebSocket subscription updated every 800ms. Clustering uses DBSCAN with dynamic parameters based on estimated hourly traffic.
03 · Widget 02 · Light Theme
The clear Modernize theme comes into play in the daily operating dashboard. Clear data on a white background: the dispatcher reads the KPIs at a glance, without visual difficulty.
The gauge is not decorative: it shows the instantaneous average speed as an efficiency proxy. Under the threshold? Automated warning. Seven days is enough time to recognize seasonal patterns.
04 · Widget 03 · Light Theme
The Design Token System is the backbone of Viantis. Built on three levels: Foundation, Primitives, Patterns. It automatically generates CSS tokens from the single source of truth in Figma.
Every color, every spacing, every beam on board has a semantic name. The dev team never sees a hex code: it sees --color-vehicle-active.
This is the first time I've seen this.
The CAN-Bus does not forgive. Each vehicle transmits 12,400 frames per second. The system must read, validate, exclude conflicts and write to TimescaleDB - all in an 80ms window.
The conflict-exclusion algorithm is deterministic: no ambiguity about which frame prevails when two sensors transmit in the same slot. Zero undefined behavior in production.
# # # # # # # # # # # #
Five layers, one data direction. Every packet that starts from a CAN-Bus sensor goes through the same deterministic pipeline: no shortcuts, no bypasses.
PostgreSQL RLS ensures that each operator only sees its own fleet. The conflict exclusion badge is not marketing, which is why the system works even with 500 vehicles simultaneously.
What I Learned
Building the tokens before the components saved weeks. Any one-time color or spacing decision, automatically spread everywhere.
80ms is not a technical requirement: it's the difference between "the system responds" and "the system anticipates". Every extra millisecond is a loss of trust.
RLS is not a layer to be added later. It must be designed in the data model from day 0. It costs ten times more to reuse it on an existing system.
Do you have a similar plan?
Let's have a little chat.
Whether it's a SaaS fleet, a design system from scratch or a complex data architecture, I bring order to the chaos.