The engineering team for everything.
Labs builds the systems and infrastructure the whole ecosystem runs on — and ships products of its own. What it ships is announced in the Journal, dated, as it lands.
Frontier work that feeds the products.
What Labs studies before it builds. Findings are written up in the Journal, including the ones that didn't pan out.
Model evaluation
Which model, for which task, at what cost. Measured on our own work, not benchmarks alone.
Agents & planning
Bounded loops: plan, act, reflect — with a reviewable diff before anything touches disk.
Memory & retrieval
What a system should keep, what it should let cool, and how to find it again.
Tooling
The small internal tools that make the rest of the ecosystem faster.
From a paper to a thing that runs.
Labs ships in phases. Each phase produces a usable increment and a dated entry. Nothing is announced before it exists.
Full-stack builds
TypeScript end to end. Desktop-first where privacy demands it.
Platforms & SDKs
Everything we ship is built on the same SDK we give out.
Gateways & routing
A model is a swappable component behind one interface, never an assumption.
APIs
Drive it from your own code. Plain HTTP, plain docs.
Local-first, by default.
The intelligence behind a product should be able to run on the user's own machine when cost or privacy says so.
Local-first runtimes
Fully offline mode. Nothing leaves unless you opt in.
Deployment
Desktop installers, self-hosted, air-gapped where required.
Observability
Per-action cost in view, full run history, budgets per project.
Security
A clear trust boundary, sandboxed execution, human-in-the-loop approval.
Build in public.Progress is dated and published — including dead ends.
Dogfood first.We use what we make before anyone else does.
Ship the minimum lovable thing.Phase-gated. Breadth comes after.
Open where possible.Code, notes and decisions default to public.
Build the next system with Labs.
From research to deployed reality. Tell us the problem.
anvecompany@gmail.com