Shadow and Skribby are both AI meeting assistants for recording, transcription, and summaries, compared here on pricing, features, and workflow fit. Shadow: A bot-free, Mac-based AI meeting assistant that transcribes and summarizes calls locally without joining as a participant. Skribby: Developer-focused meeting bot API by Skribe VOF that deploys recording and transcription bots to Zoom, Microsoft Teams, and Google Meet with bring-your-own-key transcription. They overlap on ai-meeting-assistants, so the right pick depends on team size, budget, and which meeting workflows you automate.
For ai-meeting-assistants workflows, shortlist Shadow when capturing notes and summaries across multiple conferencing platforms without a bot joining matters most, and Skribby when adding meeting recording and transcription to a saas product via api matters most. Both record across Zoom, Google Meet, and Microsoft Teams; trial each on real meetings before committing.
A bot-free, Mac-based AI meeting assistant that transcribes and summarizes calls locally without joining as a participant.
Bot-free capture that records system audio without joining the meeting as a participantCaptures on-screen content in addition to spoken audioCustomizable prompts/Skills to generate notes, summaries, and emails
Developer-focused meeting bot API by Skribe VOF that deploys recording and transcription bots to Zoom, Microsoft Teams, and Google Meet with bring-your-own-key transcription.
Bot authentication for joining restricted meetingsBring-your-own-key support for 10+ transcription providers (Deepgram, Whisper, AssemblyAI, Soniox, ElevenLabs)Meeting bots that join and record Zoom, Microsoft Teams, and Google Meet
Shadow is a free tier with paid upgrades (freemium); Skribby is a free tier with paid upgrades (freemium). Always confirm current pricing on each vendor's site before buying.
Bot-free capture that records system audio without joining the meeting as a participant
Meeting bots that join and record Zoom, Microsoft Teams, and Google Meet
Standout feature
On-device (local) transcription on macOS
Real-time transcription over WebSocket plus asynchronous transcripts
Team usage
Speaker identification during transcription
Bring-your-own-key support for 10+ transcription providers (Deepgram, Whisper, AssemblyAI, Soniox, ElevenLabs)
Integrations
Captures on-screen content in addition to spoken audio
Webhook notifications for transcripts and bot events
Languages & capture
Customizable prompts/Skills to generate notes, summaries, and emails
Speaker identification (diarization) and 30+ language support
Best-fit workflow
Webhook integration to connect outputs to other tools
Bot authentication for joining restricted meetings
Best for
Shadow
Choose Shadow if you need capturing notes and summaries across multiple conferencing platforms without a bot joining — strengths include does not add a visible bot to meetings.
Skribby
Choose Skribby if you need adding meeting recording and transcription to a saas product via api — strengths include pay-as-you-go api with no monthly minimums or contracts.
Pros & cons
Shadow
+ Does not add a visible bot to meetings
+ Local transcription keeps core audio processing on the device
- Available for macOS only
Skribby
+ Pay-as-you-go API with no monthly minimums or contracts
+ Provider-agnostic transcription via bring-your-own-key across many engines
- Cloud-only managed service with no self-hosting or open-source option
FAQ
Is Shadow or Skribby better for AI meeting notes?
It depends on your workflow. Shadow is strong for capturing notes and summaries across multiple conferencing platforms without a bot joining, while Skribby is strong for adding meeting recording and transcription to a saas product via api. Both transcribe and summarize meetings.
How do Shadow and Skribby compare on price?
Shadow is a free tier with paid upgrades and Skribby is a free tier with paid upgrades. Check each vendor's pricing page for the latest plans and free-tier limits.
Can I use both Shadow and Skribby?
Yes. Many teams run more than one meeting assistant when the workflows are complementary and the budget is justified.