How it works

Three parts. A connector on your side that hears the call, an engine on ours that turns speech into text, and your own storage where the result ends up.

During the call

The connector joins your meeting the way another participant's browser would, except it neither speaks nor appears in the room. For Nextcloud Talk it connects to your High Performance Backend as an internal client and receives one audio stream per person. That is the whole reason a transcript can say who said what: the voices never get mixed into one track.

Audio streams to the engine while the call runs. Nobody presses record, and there is no recording afterwards — see Your data.

When the call ends

1. The engine finishes recognising whatever is still buffered and produces the transcript, split by speaker, with timestamps.
2. The gateway stores it and hands it to the analyser, which writes the summary, the decisions, the open questions and the tasks. This takes minutes to a couple of hours, depending on how long the meeting was.
3. The app on your Nextcloud asks the gateway what exists, takes it, writes the files into your storage and shares them with the people who were in the call.

What crosses the boundary

Speaker attribution

Each participant's audio arrives on its own stream, already labelled by the meeting platform, so attribution is a matter of record rather than guesswork. Where a platform gives less — a shared track, a guest without a name — the line is marked as an unidentified participant instead of being attributed to somebody plausible.

The parts, named

Next