BYOK AI meeting notes for developers
Engineering and product teams often want AI summaries without turning every technical conversation into a vendor-hosted meeting record. On-device transcription handles the call locally, then lets you send only the passages worth processing to the BYOK provider of your choice.
On your device
When to keep transcription on-device
The full transcript starts on the device. Architecture details, customer names, roadmap discussion: all of it stays on the device until you decide a specific excerpt is worth sending out. BYOK stays optional, and when you do use it, only the selected text is governed by your provider's terms.
This is the right call when the meeting itself shouldn't be a cloud record, but a tightly-scoped excerpt (a summary, an issue list, a rewrite) needs the quality only a hosted model can deliver.
How it works on your device
- Record the standup, design review, or product discussion on-device.
- Review the transcript locally before sending anything out.
- Select only the passage that needs a summary, issue extraction, or rewrite.
- Send that selection through your chosen BYOK provider.
- Keep the full transcript local unless your team has approved an export or cloud-provider transcript.
With your own cloud key
For engineering teams that want provider-grade transcription and summarization on long technical calls without handing key custody to a SaaS. Pick a provider for transcription, pick another for summarization if you want, and route everything under your own API key.
When a cloud provider is the right call
When you bring your own cloud provider, jotty.pro routes audio for transcription and the transcript for summarization to whichever providers you configure. You pick from nine supported providers (OpenAI, Groq, Deepgram, HuggingFace, Ollama, X.AI, Google, Mistral, DeepSeek), and your key sets the terms that apply.
This is the right call when you need the freshest model versions, real speaker diarization on multi-participant calls, or low latency on dense technical meetings. On-device models still can't match that at scale. We don't provision or hold enterprise keys; we route requests under the key you supply.
Org-provisioned keys are supported. Your IT can issue a shared OpenAI, Groq, or other provider key; the team pastes it in Settings and every request runs under that key's terms.
The tradeoff against keeping it on-device: the provider sees both audio and transcript. You decide which provider that is, and your key sets the contract.
How it works with your key
- In Settings, pick a transcription provider and a summarization provider. They can be the same provider or two different ones; per-task routing is supported.
- Paste your BYOK key: personal, team-issued, or an org key provisioned by IT.
- Record the technical meeting, design review, or architecture call.
- The transcription provider handles audio-to-text; the summary provider processes the transcript and returns structured notes.
- The transcript writes to local DuckDB regardless of which providers handled it, ready for semantic search on the device later.
How it compares
| Dimension | On-device + BYOK summary | Generic meeting bots (Otter, Fathom) | jotty.pro with cloud-provider BYOK |
|---|---|---|---|
| Where audio goes | Stays on the device | Uploaded to the bot vendor | Routed to your chosen transcription provider under your key |
| Which terms apply | Provider terms apply only to the text you send | Bot vendor's terms apply to the whole meeting | Your chosen provider's terms apply to audio and transcript |
| Transcript residency | Local DuckDB; excerpts leave only when you send them | Vendor-hosted; export depends on vendor policy | Local DuckDB after processing; provider retains per their terms |
| Model freshness | Summary is provider-current; transcription is local | Vendor-selected models, often lagging | Both transcription and summary use provider-current models |
| Cost per meeting | Device CPU for transcription; pay only for sent text | Subscription or per-seat fee | Pay-per-use under your provider's pricing for both tasks |
Honest answers
Does BYOK undo the on-device benefit?
Only for the specific text you choose to send. The full transcript stays local; the excerpt you send to a provider is governed by that provider's terms. You can think of on-device + BYOK as "I want hosted-model quality for one paragraph, not for the whole hour."
Why not just use a normal meeting bot?
A meeting bot is fine when the vendor and data path are already approved. The on-device path fits teams that want a chance to review before any external processing happens, especially in the early stages of evaluating an AI workflow.
Can a cloud provider be used for team workflows?
Yes, but only after your team has reviewed the cloud transcript terms and decided that the content type belongs in a cloud workflow. Don't treat the configuration toggle as the approval decision.
Why not keep it on-device if I already have BYOK?
On-device transcribes locally, which is slower on long dense calls and doesn't have access to provider-grade speaker diarization. If you need clean speaker separation across a multi-participant architecture review, or your team's technical vocabulary trips up on-device models, routing transcription to a cloud provider built for it is the better path. Same DuckDB storage on the back end either way; the difference is where transcription happens.
Can I use one provider for transcription and another for summary?
Yes. Settings supports per-task provider configuration. Send audio to Deepgram for transcription, route the transcript to OpenAI for summarization, or any other combination across the nine supported providers. Each task uses the key and terms of the provider you assigned.
Whose terms apply if my company key is used on a personal device?
The terms of whoever issued the key. If your IT provisions a company OpenAI key, OpenAI's terms govern every request made with that key, regardless of which laptop kicked off the call. We don't see or store the key beyond routing the request. The audit and data-handling obligations run between your org and the provider.