A production engine, rebuilt in two weeks.

The quarter in one read: proof we ship fast, and a few things worth keeping whether or not you ever hire us.

The rebuild

2 weeksJava → Python rebuild, start to cutover

0rollbacks after launch

~50%less code, larger API surface

A client's AI music-video engine had outgrown its first codebase. Reverts were frequent and the mobile apps broke in ways nobody caught until users did.

We rebuilt it from Java to Python, contract-first and verified against the real mobile clients before a line shipped, then cut over in two weeks with nothing rolled back. If your AI product has outgrown its first codebase and now costs you speed, that is the work we do.

This quarter we shipped 116 updates to production. The team is now 20, up from 15.

Worth reading

Prompt caching, and how to think about itWhere caching saves real money and latency with large models, and where it quietly does not. → The metrics we judge AI output byHow we measure whether a model's output is good, and keep our evals honest as the product changes. → How we run a big migration without regretThe questions we answer before a rewrite, so it ships in weeks instead of stalling for a year. →

What we make

Products that are born out of our AI-first workflows.

StenoMeeting notes that write themselves, clean and searchable when the call ends.steno.unravel.tech ↗ thingShip your coding agents' output as live, commentable, versioned pages. This letter runs on it.usething.ai ↗ TabloA tiny companion that watches your AI coding agents from a corner of the screen.tablo.unravel.tech ↗

Weighing a rebuild?

Thirty minutes, and we'll tell you straight whether it's worth doing, what it would take, and how fast we could do it.

Book a call or reply to this email — it reaches us directly at kapil@unravel.tech