Comparison · Approaches, not products

Relay vs manual ticket entry

Verdict: manual entry gives one person complete control with no new tool; Relay removes the copying and keeps the source quote, but adds a service to run. If your team writes few tickets and wants zero setup, manual entry is fine. If notes regularly become tracked work, drafting with a review gate saves the retyping without giving up the decision.

By the Relay maintainers · Last updated 19 November 2026 · Relay is our product

Self-host Relay

How this comparison is framed

This page compares two approaches, not named products. The Relay column describes features that are traceable to the project's own repository. The manual column describes a typical manual workflow, not benchmarked and not measured against any team. No time-saved percentage is claimed, because no timing study was run. Where a manual process is stronger, that is stated plainly. Treat this as a decision aid, not a performance report.

Relay vs manual ticket entry at a glance

The rows below cover the parts of ticket creation that usually matter to a small team: who writes the item, what evidence travels with it, who decides the owner and where the record of decisions lives.

Category comparison: automated drafting with review vs a typical manual workflow
CriterionRelayTypical manual entry (not benchmarked)
Who writes the ticketModel drafts from notes, chat or transcriptsA person types it into the tracker
Evidence attachedSource quote linked to each draftWhatever the author pastes in
Owner suggestionUp to three ranked candidates with reasonsAuthor guesses or asks in chat
Review stepApproval gate before any pushAuthor reviews as they type
Audit trailAppend-only, hash-chained log of writesTracker's own history only
Setup effortSelf-hosted stack, trackers and chat apps to configureNo new tool to install
Source of truthYour database plus the tracker issueThe tracker issue alone

Self-host Relay

Where manual entry is stronger

Manual entry needs no new service, no credentials and no review policy. The person writing the ticket has full control over every word from the start, and there is no extraction step to get wrong. For a team that creates a handful of issues a week from deliberate written decisions, that simplicity is a real advantage. Relay is not a replacement for thinking; it is a way to move existing conversations into a tracker with less retyping.

Where automation helps

Relay captures from Slack, Discord, email and documents, then drafts tickets with the exact line that produced them. It suggests owners with reasons and routes approved items to GitHub, Linear, Jira or Notion through an idempotent outbox. The evidence and decisions stay searchable in team memory. The tradeoff is operational: you run an Apache-2.0, self-hosted stack. Hosted plans are planned, not live, so self-hosting is the working path today.

How to decide

Start by counting how often a conversation turns into tracked work. If it is rare, keep typing the tickets. If it is weekly, run the credential-free demo with a real note and compare the drafts against their quotes. Extraction on messy multilingual fixtures measures about 0.78 precision and 0.75 recall, so expect to edit some drafts. If that editing is still less work than writing from scratch, the automated path earns its setup cost.

Final verdict

Neither approach is universally better. Manual entry wins on control and zero setup; Relay wins on traceability and repeated capture. The honest test is your own volume of notes and the quality of the drafts on your content, not a generic productivity claim.

Self-host Relay


Methodology: repository-grounded comparison. Relay facts come from the project's README, workflow, hosting and auth docs. The manual column is a described general workflow, not a measured baseline. No named competitor, price, rating or time-saving figure is used.