Oolong®

Oolong Technologies is building the infrastructure for the agentic age.

An AI-first, deep-tech practice for distributed training and inference — and a lab that publishes everything it learns along the way. We build the durable systems behind agentic products, then write up how they work.

Est. 2026 Distributed Training & Inference Agentic Systems

01  /  Services

Agentic AI

We design and ship agentic systems that do real work: planning, tool use, and long-horizon execution that holds up outside the demo. The interesting problems are rarely the model — they are memory, control flow, and recovery.

From retrieval to evaluation harnesses, we build the scaffolding that turns a capable model into a dependable one, and we instrument it so you can see exactly why it did what it did.

Platform Engineering

Distributed training and inference is an infrastructure problem first. We build the schedulers, data planes, and GPU fabrics that let teams train and serve large models across heterogeneous, commodity hardware.

The goal is leverage: elastic capacity, sane cost curves, and a platform your researchers can drive without a systems team standing behind them.

Durable Workflows

Long-running, fault-tolerant pipelines are where most ML systems quietly break. We model them as durable, replayable workflows — immutable steps that survive restarts, partial failure, and the occasional cloud outage.

The result is work that resumes instead of restarts, with an audit trail you can actually reason about months later.

02  /  Approach

We don’t just ship the system. We publish how it works.

Most consultancies hand you a black box and a invoice. We think the more valuable artifact is understanding: the architecture decisions, the benchmarks, the dead ends. Knowledge that compounds for your team long after the engagement ends.

So we work in the open. Every engagement produces a system and a body of writing — field reports, reproducible experiments, and the occasional strong opinion about how distributed AI infrastructure should be built.

iOpen by default

We publish methods, benchmarks, and the failures — not just the wins.

iiReproducible

Every result ships with the runbook, the seeds, and the raw logs.

iiiDistributed at the core

Built for many machines from the first commit, not retrofitted later.

ivAccountable & observable

If we cannot measure it and explain it, we do not ship it.

03  /  Writing & Experiments

All writing
Research Oct 2024

RAG systems have a recall problem, not a hallucination one

Stopping hallucinations are only half of the target of information retrieval systems

Fig. 1 — Cost vs. latencyn = 46 runs