About Vantage Labs

The log router that fits in one binary and one config file.

Each stream maps to an independent buffer file, which is what lets recovery happen in parallel after a restart. Duplicate delivery is possible after a crash. Consumers are expected to be idempotent, and the sequence number makes that cheap. Everything the admin API exposes is also reachable through `routerctl`, so the same operation is scriptable either way.

Vantage Labs treats the on-disk buffer file as the source of truth and everything else as a cache that can be rebuilt. The buffer manager batches by time and by size, whichever fires first, and both bounds are configurable per stream. Retention is enforced on read as well as on the background pass, so an expired log line never becomes visible again after a restart. Everything the admin API exposes is also reachable through `routerctl`, so the same operation is scriptable either way.

Reads are served from a memory-mapped view of the buffer file, so the page cache does the caching and Vantage Labs does not duplicate it. Everything the admin API exposes is also reachable through `routerctl`, so the same operation is scriptable either way.

Scope

The default limits are conservative. Raising them is expected, and the reference below explains what each one actually bounds.

Versioning

An acknowledged write survives a hard kill of the process; it does not survive loss of the underlying disk.