Groq switch cut API cost 30%. Production stays on gpt-4o. Monthly cap set at $30.
AI meeting notes?
Just grab an API key.
Turn every meeting into Markdown

Data stays local. Even a free-tier key is enough.
API keys are free.、
、Yet meeting tools still wanta monthly subscription.
OpenAI, Gemini, Groq — generate a key and you're on pay-as-you-go or a free tier. But the moment you want meeting notes, it's $20/month SaaS. Output locked in proprietary format. Audio shipped to their cloud.
Sound familiar?
- API key would do, tool charges monthlyFixed cost for a pay-as-you-go task
- Output is PDF or proprietaryWon't open in Obsidian
- Audio uploaded to their cloudYour conversations, their servers
- Provider locked inCan't switch to new models
Run it on what you already have
API key + local machine. That's it.
- ✓Paste your key. Free-tier works too
- ✓Output is Markdown. Obsidian, Git, whatever
- ✓Audio stays local. Never leaves your machine
- ✓Switch providers in one setting
With Reki,meeting notes work differently
Paste your key. Done.
OpenAI, Gemini, Groq. Free-tier keys work. No subscription. That's it.
Saved as .md. Do what you want with it.
Drop it into your Obsidian vault. Push it to Git. Grep it. Whatever you do with Markdown, it just works. No proprietary format locking you in.
1. Dev environment switches to Groq (Whisper)
2. Production stays on gpt-4o-transcribe
3. Monthly cost cap set at $30
Your audio never touches Reki's servers.
This is what makes Reki fundamentally different. Audio is stored on your Mac. Transcription is sent directly from your machine to the AI provider you chose. It never passes through Reki's servers. We never see the contents of your meetings.
- TodayEngineering StandupAPI cost optimization...
- 3d agoTech ReviewGraphQL migration PoC plan
- Last weekArchitecture ReviewMicroservice split decision
- 2w ago1:1 / Tanaka & MatsushimaHiring plan revised
- Last monthInfra PlanningSupabase migration decided
Any meeting tool. As-is.
OS-level audio capture. No bot invite needed.
SaaS vs DIY vsReki.
| Features | Reki note | SaaS (Otter / Fireflies etc.) | DIY Script / CLI |
|---|---|---|---|
| Bring your own API key | Runs on your key | Subscription required | Build it yourself |
| Output format | Markdown | Proprietary | You implement it |
| Data storage | Local (no relay) | Cloud required | You configure it |
* Conceptual comparison
You pick
the provider.
- ✓Switch in one setting
- ✓Free-tier keys work too
- ✓More providers coming
Paste your key. Hit record.Get .md files.
Tanaka:Auth protocol decided — going with OAuth 2.0. GraphQL migration PoC starts next week.
Matsushima:DB schema changes are involved, so I'll run the migration script tests first.
Suzuki:Blue/Green deploy environment will be ready by Friday.
Meeting name, attendees, and tool auto-linked
Search across all past meetings
"What did we decide last week?" — answered
.md per meeting. Searchable decision log
Tanaka:Auth protocol decided — going with OAuth 2.0. GraphQL migration PoC starts next week.
Matsushima:DB schema changes are involved, so I'll run the migration script tests first.
Suzuki:Blue/Green deploy environment will be ready by Friday.
Meeting name, attendees, and tool auto-linked
Search across all past meetings
"What did we decide last week?" — answered
.md per meeting. Searchable decision log
No subscription needed.
Just an API key.
Data stays on your machine. Output is Markdown.
Auth protocol: OAuth 2.0 decided. GraphQL migration PoC starts next week. DB migration script test first.
Q3 hiring plan revised. One engineer hire instead of two. Remaining budget goes to AI infrastructure.
Groq switch cut API cost 30%. Production stays on gpt-4o. Monthly cap set at $30.
Auth protocol: OAuth 2.0 decided. GraphQL migration PoC starts next week. DB migration script test first.
Q3 hiring plan revised. One engineer hire instead of two. Remaining budget goes to AI infrastructure.