Comparison · Approaches, not products
Relay vs generic AI notetakers
Verdict: a generic AI notetaker is built to produce a summary; Relay is built to produce a reviewed ticket in a tracker. Notetakers are usually better at transcription and prose. Relay deliberately starts after the transcript, turning what was said into evidence-backed work that a person approves before it is pushed.
How this comparison is framed
This page compares categories, not named products. The Relay column is traceable to the project's own repository. The other column describes generic AI meeting assistants as a class, with no vendor named, no price, no rating and no claim that one product is worse than another. The rows describe what each approach is designed to output. Nothing here is a measured comparison of specific tools.
Category comparison at a glance
The useful distinction is where each approach stops. A notetaker usually stops at a readable record of the meeting. Relay continues into a tracker, carrying the source quote and an approval step with it.
| Criterion | Relay | Generic AI meeting assistant |
|---|---|---|
| Primary output | Reviewed ticket with evidence | Summary or transcript |
| Pushes to a tracker | GitHub, Linear, Jira, Notion | Typically not the primary job |
| Evidence kept | Source quote on each draft | Usually the transcript itself |
| Ownership | Ranked candidates with reasons | Not a usual output |
| Approval gate | Required before a push | Not applicable to a summary |
| Open source / self-hostable | Apache-2.0, self-hosted first | Varies by product |
| Data location | Your database and your chosen provider | Varies by product |
Where generic notetakers are stronger
If you need an accurate transcript or a well-written meeting recap, a dedicated notetaker is the right tool. That is the job those products are built around, and many do it well. Relay does not compete on transcription quality. It accepts transcripts, VTT and SRT files, transcript JSON and notetaker exports as inputs, then works on the part that comes after: deciding what should become tracked work. Using both together is a reasonable setup.
Where Relay starts
Relay starts when the conversation already exists as notes, chat or a transcript. It drafts tickets with a title, type, priority and owner, attaches the supporting quote and holds the draft for review. Approved items go through an idempotent outbox so one draft becomes one issue. Decisions and commitments remain searchable with their sources in team memory. It is Apache-2.0 and self-hosted, with no feature gates on the open-source path.
Is a hosted service available?
No. Relay's cloud plans are planned, not live. Plan limits are enforced in the API, but signup and billing are opt-in per instance and the waitlist is closed. Self-hosting is the working path today. This matters for the data-location row above: with Relay, you choose the database and the provider, because you run the stack yourself.
How to decide
Ask what you need from the meeting. If the answer is a readable record, use a notetaker. If the answer is tracked work that someone owns, try Relay on the same notes. Extraction on messy multilingual fixtures measures about 0.78 precision and 0.75 recall, so check drafts against their quotes before approving. The two tools solve different problems, and the comparison is about outputs, not about which category is better overall.
Final verdict
Notetakers and ticket automation are complementary. Relay is not a better summariser; it is a way to turn what was said into reviewed, attributable work in your tracker. If that is the gap in your workflow, self-host it and judge the drafts on your own content.