Reki noteReki note
Join the Waitlist

AI meeting notes?
Just grab an API key.

Turn every meeting into Markdown

Reki note

Data stays local. Even a free-tier key is enough.

Mac Early AccessWindows Coming soon
The Problem

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.

Before

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
Result
An API key would do, but you're paying monthly
The tool decides, not you
After

Run it on what you already have

Reki note

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
Result
No monthly bill
Pay-as-you-go only
Benefits

With Reki,meeting notes work differently

01Right after setup

Paste your key. Done.

OpenAI, Gemini, Groq. Free-tier keys work. No subscription. That's it.

NOTIFICATION
Meeting detected
AppZoom Meeting
CalendarBackend API Review
02After each meeting

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.

What action items came out of today's standup?
ANSWER
Three decisions were made:
1. Dev environment switches to Groq (Whisper)
2. Production stays on gpt-4o-transcribe
3. Monthly cost cap set at $30
Source: Engineering Standup 5/7 10:00
03Always

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.

MEETINGS
  • Today
    Engineering Standup
    API cost optimization...
  • 3d ago
    Tech Review
    GraphQL migration PoC plan
  • Last week
    Architecture Review
    Microservice split decision
  • 2w ago
    1:1 / Tanaka & Matsushima
    Hiring plan revised
  • Last month
    Infra Planning
    Supabase migration decided
Works With Your Stack

Any meeting tool. As-is.

OS-level audio capture. No bot invite needed.

Zoom
Google Meet
Teams
Discord
Slack Huddle
Other apps on device
In-person meetings
Import audio files
Other audio sources
Compare

SaaS vs DIY vsReki.

FeaturesReki noteSaaS (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

Your Choice of Provider

You pickthe provider.

  • Switch in one setting
  • Free-tier keys work too
  • More providers coming
PROVIDERS
Use what you already have
OpenAI
Gemini
Groq Cloud
OpenRouter
NVIDIA
+ More coming soon
How it Works

Paste your key. Hit record.Get .md files.

Input 01
Meeting Audio
00:03

TanakaAuth protocol decided — going with OAuth 2.0. GraphQL migration PoC starts next week.

00:18

MatsushimaDB schema changes are involved, so I'll run the migration script tests first.

00:34

SuzukiBlue/Green deploy environment will be ready by Friday.

Input 02
Calendar Info
Backend API Review
Date2026/05/07 13:00
AttendeesTanaka, Matsushima, Suzuki
ToolGoogle Meet

Meeting name, attendees, and tool auto-linked

Output
Markdown Knowledge Base
Full-text search

Search across all past meetings

AI Q&A

"What did we decide last week?" — answered

Knowledge log

.md per meeting. Searchable decision log

No subscription needed.
Just an API key.

Data stays on your machine. Output is Markdown.

Mac Early AccessWindows Coming soon
Home
Every meeting record, in one place.
Backend API Review
5/6 13:00–14:00· Google Meet· 4 people

Auth protocol: OAuth 2.0 decided. GraphQL migration PoC starts next week. DB migration script test first.

1:1 / Tanaka & Matsushima
5/5 16:30–17:00· In-person· 2 people

Q3 hiring plan revised. One engineer hire instead of two. Remaining budget goes to AI infrastructure.

Ask RekiEnter meeting
What action items came out of today's standup?