Pricing
Your product ships
with meeting notes.
One API key. Bot joins, transcript delivers, webhook fires to your server. Pay per second — $200 free to get started.
+ £0.50 per hour captured
$200 free credit · no card required
+ £0.50 per hour captured
$200 credit applied · cancel anytime
Shipping at volume?
Volume pricing, SLAs, and self-hosted deployment for teams that need them.
Why Gregnote
One API vs. multiple vendors.
| Feature | Gregnote | Recall.ai | Deepgram |
|---|---|---|---|
| Meeting bot | — | ||
| STT transcription | — | ||
| Single API key | — | — | |
| Signed webhooks | — | ||
| Self-hosted audio | — | — | |
| Per-second billing | — | ||
| No monthly minimum | — | — | |
| Price / hour | £0.50 | ~£2.80 | ~£1.40 |
Prices estimated at standard list rate. Recall.ai charges per bot-minute. Deepgram charges per audio-second.
Billing
questions.
The clock starts when the bot joins and audio capture begins. It stops when the meeting ends or the bot leaves. Waiting in the lobby is free. Billing is per-second, always rounded down.
Every account starts with $200 free — enough to capture 400+ hours of meetings before you spend a penny. No card required until the credit runs out.
No — Pro is a £9/month add-on that unlocks the extras. You still pay £0.50/hr for what you capture. Think of it as paying for the brand and the faster line, not for the hours.
No. Bot capture and transcription share one rate: £0.50/hr based on the audio duration. Uploading a standalone audio file is billed the same way. There is no separate STT charge.
New bot requests pause until you add a payment method. Everything already captured stays accessible — transcripts, webhooks, your API keys. Nothing is deleted.
By default the bot appears in the meeting participant list as 'Gregnote'. With Pro you set any name you like — your product name, your company name, whatever fits the experience you're building. Your users see your brand, not ours.
Yes. Self-hosted deployment, volume pricing, and SLAs are available for teams with higher volume or stricter data requirements. Email [email protected] with your expected usage.