Your Oris, in numbers
A new card in the app shows how you've used Oris — including the one stat only a two-track recorder can tell you: how much of the conversation was you.
writing
Build-in-public posts, technical deep-dives, and reflections on making indie software that respects the people who use it.
A new card in the app shows how you've used Oris — including the one stat only a two-track recorder can tell you: how much of the conversation was you.
If you're on the waitlist, you're in first. A local-first Mac app that records both sides of a call and lands clean notes in your Obsidian vault.
We rewrote Oris's transcription and summarization engine from Python to Swift one module at a time — built with Anthropic's Claude Opus 4.8 through Claude Code and dynamic multi-agent workflows, with the old pipeline kept as a byte-for-byte reference and a separate frontier model reviewing every PR. Here is what that actually looked like, including the bug that survived a green test suite, a code review, and an integration test.
We replaced Oris's ~1.2GB Python stack with a single 67MB native binary. Transcription and summaries both run on-device through Apple's frameworks, your meeting audio still never leaves your Mac, the transcripts came out cleaner — and as a bonus the engine now runs on roughly twelve more macOS versions than before.
Oris summarizes with a provider you choose, billed to you, on a key you hold. That's a permanent architectural commitment, not a launch promo.
How a Mac can record both the mic and system audio into one dual-track file without anyone joining your call.
The default for every meeting tool is to upload your audio to a server. Oris starts from the other side of that default.
No posts in this category yet.