Open-source org
xtream-codec is the connection-layer foundation; data governance and an EV fleet agent stack on top. Finish a full conversation in the browser. JT/T 808 in the same entry is still on the roadmap.
Open to try
JT/T 808 codecs
Desktop packet lab
Project matrix
Solid connections and codecs first, then telemetry and the fleet agent. Each layer can be verified on its own. Dashed lines are planned: 808 in the same entry, a reference architecture, more protocol decoders.
Solid = shipped · Dashed = planned
Intelligence
Agent
vehix-agentTalks to people
First vertical: EV fleet ops. Query, diagnose, approval-gated commands. The demo uses GB/T 32960 and UDS; long-window history comes from the data layer, not mocks.
Roadmap: 808 and approval in the same conversation. The business layer never parses the binary.
LiveData
Data governanceM1 prototype
Land in the lake, then let the agent query
Simulator events go to Kafka, Flink writes Iceberg; UI and Agent query ~30 days via Trino — no mock history. Trusted data makes the agent smarter.
Short window stays OLTP · Long window uses the lake
Device
Simulator
Roadmap
MCP bridge
Roadmap: JT/T 808 in the same entry. vehix calls REST only — it never parses the binary.
Connect
Foundation
xtream-codecTalks to protocols
Connection-layer foundation. Async TCP/UDP codecs, JT/T 808 server and Dashboard; repo under hylexus.
Roadmap: more heterogeneous vehicle protocols. What ships today is 808 codecs and the server.
Device
Vehicle terminal
Sidecar
Talks to the wire · Sidecar debug — not on the data path
Roadmap: modular JT/T 808 / 1078 / 809 / 905 decoders.
Intelligence
Agent
vehix-agentTalks to people
First vertical: EV fleet ops. Query, diagnose, approval-gated commands. The demo uses GB/T 32960 and UDS; long-window history comes from the data layer, not mocks.
Roadmap: 808 and approval in the same conversation. The business layer never parses the binary.
LiveData
Data governanceM1 prototype
Land in the lake, then let the agent query
Simulator events go to Kafka, Flink writes Iceberg; UI and Agent query ~30 days via Trino — no mock history. Trusted data makes the agent smarter.
Short window stays OLTP · Long window uses the lake
Device
Simulator
Roadmap
MCP bridge
Roadmap: JT/T 808 in the same entry. vehix calls REST only — it never parses the binary.
Connect
Foundation
xtream-codecTalks to protocols
Connection-layer foundation. Async TCP/UDP codecs, JT/T 808 server and Dashboard; repo under hylexus.
Roadmap: more heterogeneous vehicle protocols. What ships today is 808 codecs and the server.
Device
Vehicle terminal
Sidecar
Talks to the wire · Sidecar debug — not on the data path
Roadmap: modular JT/T 808 / 1078 / 809 / 905 decoders.
Direction
Not shipped products
Near-term
Fold what already runs into a deployable reference architecture and cut integration complexity.
Matrix
Grow access, edge, governance, security, and visualization around the connection-layer foundation.
Long-range
Interoperable and trustworthy. Direction—not a finished operating system.
What we build
High-throughput networking and codecs should be independently verifiable, then telemetry and AI ops. What runs today is codecs, a packet lab, an agent demo, and an M1 lake prototype. JT/T 808 in the same conversation is still a planned MCP bridge.
vehix-agent
An EV fleet agent with a simulator. LangGraph orchestrates MCP tools. Finish a full conversation in the browser.
AI roadmap
MCP + LangGraph today. JT/T 808 over MCP is still on the roadmap—design docs are not a shipped feature.
Hi, I'm Vehix—your fleet ops assistant.
Ask about fault diagnosis, vehicle commands, OTA, or fleet stats. JT/T 808 commercial-vehicle access is still on the roadmap.
xtream-codec
Async TCP/UDP codecs. JT/T 808 server and Dashboard. Repo under hylexus; docs hosted here.
net-octo
A desktop TCP/UDP lab, beta published. On the roadmap: modular 808 / 1078 / 809 / 905 decoders. Not on the data path.
Hey operator!
What’s next for vehix-agent
In flight:
MCP-bridge xtream-codec (roadmap)
Design written up in the repo
Start here
FAQs
Short answers. Details live in each repo’s README.
Try the vehix console, or help fold connection, data, and ops into one reference architecture.