Ryva reads your GitHub and Slack so you can kill your standups

Name: Ryva reads your GitHub and Slack so you can kill your standups
Availability: InStock
Author: egeuysall

by egeuysall·Mar 8, 2026·1 point·0 comments

Visit Project View on HN

AI Analysis

●●SolidSolve My ProblemShip It

Standup replacement via GitHub+Slack signals, but the decision isn't whether Slack summaries work—it's whether teams trust async.

Strengths

•Identifies a real pain (5 status standups × 10 people × 30 min = 25 hours/week) that most async teams feel acutely
•Decision-traceable design (blocks with domain, priority, outcome) moves beyond activity summary toward governance
•Free tier + clear usage metrics (20+ decisions/week, 10 hours reclaimed) set reasonable expectations upfront

Weaknesses

•Core blocker is organizational adoption culture, not product: teams that value written context already kill standups themselves
•No technical differentiation vs. Claude/GPT reading GitHub/Slack API and summarizing—the heavy lifting is existing LLM infra
•Early access status + no evidence of product-market fit; unclear if decision framing actually prevents meetings or just creates busywork

Post Description

Hey HN,

I built Ryva because I kept seeing the same problem across dev teams.

The actual state of the project lives across commits, PR discussions, and Slack threads. Nobody pulls it together. So teams hold a daily standup to reconstruct it verbally instead.

Ryva connects to GitHub and Slack, reads those signals, and generates a written project state showing what changed, what decisions were made, what decisions are still missing, and what needs attention next.

The goal is not to summarize activity. It is to replace the reconstruction meeting with something that already exists before the meeting starts.

Still in early access. Happy to answer any questions.