Recall is, at its core, an API for bot recording. As someone building an application that relies heavily on conversational data, recording meetings is really important. Recall makes that process as easy as an API call, standardized across various meeting platforms. It's a huge PITA to set up infrastructure to get bots to join meetings that handle each platforms' proclivities, encoding and storing video data, etc.
The transcription service is just something they do to make transcribing recordings - one of the most common first post-processing steps for any conversational data - easier and lower friction.
I actually agree that it’s become incredibly easy to transcribe conversations using open-source models, and that’s not where Recall adds the most value. The hard part is building the infrastructure that allows you to get real-time access to the raw audio, video, and transcript data directly from the meeting platforms. We abstract all of that away and provide you with a clean interface to access that data. Once you get the data, you could use any of the models that you mentioned to do your own transcription, or transcribe using Recall’s transcription models.
No but seriously, y'all have built not only an incredible product that I had the chance to demo, but a great company as well, through your previous pivots and cofounder changes. You're building schlep tools that product companies _definitely_ don't want to do, years before it was clear there was a market here, and do it well.
There's definitely demand for a native screen recorder, and I think it's the right move to be agnostic to privacy (the lower down the stack you go, the more permissable you should be about use-cases). Imagine how much competition in file storage there would have been had there been an API provider for Dropbox's Finder sync technology (though you could argue it just incentivizes large companies like Hubspot to build their own screen recording feature into their platform, rather than enabling new startups like Gong but I digress).
Y'all deserve the success that you have, and wishing you all the best of luck with the new product launch!
Congrats on the launch! :tada:
Because consent laws are complex and vary by region and industry, we leave the consent flow to the developer and we provide the tools and guidance to do it correctly. As with our Meeting Bot API, we also urge teams to follow local laws and make recording clearly visible to users
Consult Linda Tripp
Both why send it and why send it with very little info included on the page?
Instead, we built a single API that can get the same results without the issues mentioned above so you can focus on building the features your users care about