HTTP runtime
Routes, middleware, static files, health checks, and JSON APIs run through the Vix application layer.
Vix.cpp runtime app
Native C++.
A real backend runtime.
Pico is a compact C++ backend built with Vix.cpp. It runs HTTP routes, durable KV state, SQLite events, background jobs, and WebSocket diagnostics — in one process you can inspect live.
$
One small app, several runtime layers.
Pico exists to exercise the parts of Vix.cpp that only show up in a running process — not a demo that mocks them away.
Durable state
Runtime counters and KV values persist through restarts, so you can watch state survive a reboot.
Live diagnostics
The dashboard exposes metrics, events, ThreadPool jobs, and WebSocket checks straight from the browser.
What runs inside Pico
Every layer is a real Vix.cpp subsystem, wired together in one binary.
HTTP server
Routing, middleware, and JSON responses on the Vix app layer.
KV + SQLite
Durable counters in KV; an append-only event log in SQLite.
ThreadPool jobs
Background work submitted to the Vix ThreadPool, with metrics.
WebSocket
A realtime channel with live diagnostics from the browser.
Endpoints
Hit them directly, or drive them from the dashboard.
GET /api/health
GET /api/status
GET /api/threadpool
GET /api/events
GET /api/events.csv
GET /api/ws/metrics
See the runtime, live.
Open the dashboard to write KV values, run jobs, exercise auth, and watch events land in SQLite — in real time.