Zero Dev Group
Our stack
Every system on this page is ours: written, run and maintained in-house, on our own operations. Status is stated plainly, and the numbers were measured from the code on 3 November 2026.
How it connects
The systems
In service
The conduit
Fetch, normalize, store. Every byte of outside data enters through one registered source list and is banked into one SQLite file per domain, with map tilesets kept as plain files beside it. No AI in the pipe: fetching is deterministic code.
Rust · clap · rusqlite · tokio
26,543 lines of Rust · 245 test functions · 23 registered sources
In service
The clock
Decides when, never what. Calls the conduit on each feed's cadence, one feed at a time, skips anything still fresh after a restart and backs off on repeated failures.
Rust · rusqlite · no async runtime
577 lines of Rust · 2 test functions
In service Demo upon request
The map server
A self-hosted map product: our own PMTiles basemaps, live USGS gauge and earthquake layers, tides, weather and aerial imagery, served by one binary to a MapLibre GL front end with no CDN.
Rust · axum · MapLibre GL · PMTiles
5,119 lines of Rust · 5,919 lines of front end · 59 test functions
In development Demo upon request
Field telemetry
Boat operations and a small scout vessel. An on-board GNSS logger records the track, stores it and forwards it ashore, where the conduit digests it into the store and the maps read it back.
C++ firmware (PlatformIO) · Python tools
Logger firmware v0.1.0 · 1,413 lines of firmware and tools
In service
The workbench
Our internal console: a file vault browser, a real terminal, the bench log every agent and engineer writes to, and map-source administration. Home network only, by design.
Rust · axum · plain JavaScript
6,097 lines of Rust · 65 test functions
In service
AI on the premises
Large language models running on our own four-core machine, CPU only, behind an OpenAI-compatible API. Prompts stay in the building unless we choose a hosted provider for a task.
Rust · llama.cpp · GGUF models
803 lines of Rust
In service
Build and deploy
Pulls, commits and pushes across all eleven of our repositories, and installs each service from its own deploy script, locally and never by force.
Rust · clap
773 lines of Rust · 8 test functions
In development
The public face
One Rust server and plain HTML and CSS. Nothing loads from another origin, there are no trackers, and our internal systems publish to it one way.
Rust · axum · static HTML and CSS
1,110 lines of Rust · 28 test functions
How we build
Every outside feed is named in one registry. If it isn't registered, it doesn't enter.
Fetching and normalizing are deterministic code. Intelligence works at the edges, never in the data path.
One SQLite file per domain and map tiles as plain files. Copying the store is a backup.
Internal tools never face the internet. The public site is its own host, and publishing runs one way.
Work with us
Engagements by arrangement.