Orin
Imagine a morning radio show that exists for an audience of exactly one — you. Two hosts talk you through what landed in your inbox overnight, what's on your calendar today, and the news you actually follow, while you make coffee. It's made fresh every morning, about you, for nobody else.
By the time I paused it, it had grown from a single daily briefing into a personal podcast platform — multiple shows, each with its own cover art and show notes, an episode feed, and one-off episodes you can ask for on demand.
Two hosts, not a text-to-speech robot
A briefing you listen to has different rules than a feed you scroll. Two hosts talk through your morning the way a good radio duo would — one carries the facts, the other pushes back, asks the obvious question, connects it to yesterday. It's generated fresh every day, for exactly one listener.
Memory
Orin builds context over time. It learns which newsletter you never care about, which project the recurring Thursday call belongs to, which topics deserve thirty seconds instead of five. The tenth briefing should know you better than the first — that's the entire bet.
Private by design
Your inbox and calendar are the most personal data you have. Orin has no ad model and sells no data — the product is the briefing, not you. That constraint shapes the architecture, not just the privacy policy.
Where it came from
Orin started as Receipt AI — AI summaries printed on thermal receipt paper at 7 a.m. The printer worked. The idea deserved audio.
Stack
A Rust streaming core with Bun and TypeScript services around it, and native apps on both platforms — SwiftUI on iOS, Kotlin on Android, at feature parity.
Why it's paused
The whole pipeline works end to end — briefings generate, shows stream, both apps play them. It never launched past the waitlist, and other projects took the front burner in August 2026. It's parked, not abandoned.