Company
Why we started Oruve
A short note on the gap between how production looks on paper and how it actually behaves.
Engineering deep-dives, product thinking, and a few opinions on what print infrastructure should look like in 2026.
A short note on the gap between how production looks on paper and how it actually behaves.
Counting the engineering time you'll never get back, and how to break the cycle.
Why Oruve logs every state change, and what becomes possible when you can replay the entire history of an order.
A framework for deciding provider strategy: economics, redundancy, and the diversity trade-off.
How the print industry can learn from logistics, ride-sharing, and the problems that others solved a decade ago.
What changes when adding a provider takes days instead of months, and why it matters for how print businesses work.
How Oruve tracks order state across 14 providers with eventual consistency — and why it matters when providers disagree.
How to design your system so adding or switching providers doesn't require rearchitecting your product.
When custom adapters make sense — and when they're just technical debt with a premium label.
Why the industry never invested in infrastructure, and what's finally changing.
Why the biggest fulfillment channel in ecommerce runs on 1990s infrastructure, and why that's finally unsustainable.
One email, every other Tuesday. New writing on print infrastructure, distributed systems, and the work in between.