Alternatives
Products that do what I built a standup app so I'd stop switching between Linear,GitHub,Slack does
We are a small team and my standup workflow was: open Linear, find who's working on what, switch to GitHub, check PRs, switch back, share my screen, ask people to give updates they could've just typed. All so I could answer "what's everyone doing and is anything stuck." So I built a thing where I just ask. "How's the team" pulls up an overview. "What's Avi working on" shows their issues sorted by status with their PRs. "Anything at risk" shows stale and unassigned work. It renders actual interactive components, not chat responses, I can filter by status, priority, repo, whatever. The whole…
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8CA
I built this because I was tired of creating pull requests in 20 repositories just to change a single line of workflow job version. With Infra as AI, just mention the change. Agents work on all repos in parallel, read the docs, make a bunch of PRs and fill in the description. You can see the demo of the actual dashboard in the landing. Let me know your thoughts :) It means a lot to me!
Sep 2025 · infrastructureas.ai
- 9GL
I've always dreamed about a project like that when looking at status boards at other companies. We finally had the time to do our own. Here are some photos: http://www.flickr.com/photos/robert_olejnik/sets/72157633736087905/ The stack: Django, mustache.js, Chart.js, Bootstrap and custom Supybot plugin. Maybe will be inspiration for someone else ;-) Do you guys have similar status boards? Cheers, Robert.
2013
- 10RK
Hi HN! We’re Jake and Akshay, co-founders of Rendevu (https://rendevu.co). In our experience, as teams grow it gets increasingly difficult for everyone to stay in the loop while also easily finding all of the information that they need to continue executing. Some teams try to solve this issue with tools like Slack, but the synchronous nature of a chat app result in members of the team often missing or losing files and information. The chat interface also does not easily support two-way interactions with your other tools. At the core, the focus of the app is this full…
2018
- 11BP
We got tired of not being able to accurately answer "When will this be done?" and "Will anyone be required to work overtime on the current schedule?", or spending too much time in meetings and standups trying to answer those questions. Just opened up for beta. Would love some opinionated developers to guide future improvements (or feedback on the general idea).
2022 · projectburndown.com
- 12TM
Figured I'd track the popular coding agents to see merge and approval rates. At first I was tracking Opened vs. Approved, but realized most people aren't approving; they just merge. I haven't found a way to reliably track the other agents (Jules, Devin, etc), since they don't have a standardized branch naming convention. Interesting to watch this over time. Open to ideas.
2025 · github.com
- 13GP
As a front-end engineer that worked in multiple product teams, there are a lot of discussions between PM/Designers/Engineers made to ensure everyone's aligned before features/fixes are shipped. I'm building a tool to make this process easier, so teams can ship faster. Ditch the screenshots/screen recordings, and simplify communication in a single tool. Got some features in mind, but I wanted to get some thoughts from the HN community. Thanks for checking it out! Happy to answer any questions.
2022 · pageblox-app.vercel.app
- 14IB
Hi HN, I've been working on this for a while and it was hard to decide when to stop, either on the way information is presented or when to stop with adding entries. It's not meant as a blog, but rather as a reference that keeps growing. Link: https://thehardparts.dev Currently I've created 4 main section: - Failure Modes: ways project go wrong - Red Flags: early signals that are worth taking seriously - Tech Decisions: common and not so common trade-offs for hard choices - Playbooks - guided approach for situations that repeat I've also focused on creating links between them to…
Apr 2026 · thehardparts.dev
- 15IB
I’ve spent the last 2.5 months building a product that runs LLM-powered code reviews on my pull requests — and I just launched it. The tool is built specifically for solo developers. You install it on your repo, trigger a scan by creating a pull request, and it leaves structured review comments using OpenAI under the hood. Funnily enough, I used the dev version of this app to review its own pull requests while building it. It helped me spot bugs, simplify structure, and keep quality high — all with minimal need for another human in the loop. Things I want to try out in the next months : -…
2025 · codii.dev
- 16CB
2021 · codeapprove.com
- 17
- 18IB
Hi HN, When I was in FAANG, I despised ticketing. I was always the eng that refused to update. Then when I was a tech lead, I had the pain of pinging everyone for updates because they hated it too. Things would go out of date, and then no one would really know if we were on track. We also had little visibility into what the team was doing outside of pinging/standups. So I made an AI that looks at every commit you push and updates tickets for you. It can create tickets if there isn't one, update, leave comments, tag associated commits etc... Basically, it's an "AI Board Babysitter" so…
2025 · usevectra.com
- 19ZS
Hi HN, I’m Tobi. For a couple of hours over the past few days I’ve been hacking on something to fix a pain point in my dev workflow: writing status updates. Progress is invisible by default. GitHub, Linear, Jira all track tickets and code, but they don’t do a good job of capturing the narrative between “ticket started” and “ticket done.” You start working on a feature, your PM asks “how’s it going?”, and even though you know exactly how it’s going - because you’ve been committing and making progress - you still struggle to answer. That usually means breaking your flow to piece together an…
2025 · zyg.sh
- 20HA
Hey guys, I left my PM job in December to learn how to code. The plan, - Build something that "I" could build with my background (I haven't studied CS) - Something that already existed and I used so I didn't have to spend time finding PMF Over the past 4 months I've been building howsthisgoing.com (a standup bot for slack with AI summaries). My ex-employed signed up in May & I got another customer through a university batchmate sometime in June (the company he's working at). However, since then it's mostly been 0 new customers, I get roughly 6-10 views on my site daily. The bot and my…
2024 · howsthisgoing.com
- 21IB
Hello HN! I got pretty overwhelmed with Notion, Trello, etc. (Even though they are great tools!) as an indie dev, so I built an app that is simpler to use and perfectly suited for an indie like me :) You can basically divide your projects into multiple milestones (a milestone could be e.g. a new version), and the milestones can have multiple tasks that are either todo, in progress, or done. The progress for each milestone is calculated with those tasks, and you can also prioritize and categorize the tasks using tags (E.g. for me, #ph turns into "High Priority", and #pm into "Medium…
2024 · apps.apple.com
- 22BA
I kept failing at building in public for the same reason every time: not fear of judgment, just the blank page after a long day of shipping. Something always happened. But converting "refactored auth flow" or "fixed that edge case that's been annoying me for a week" into something worth posting felt like a second job on top of the actual job. So I'd skip it. Then skip it again. Then stop entirely. The approach: connect your GitHub, it pulls recent commits and repo activity, and generates draft posts for multiple platforms in your tone — raw founder voice, not content creator polish. The idea…
Mar 2026 · smashlanding.xyz
- 23
Hey HN! What does a regular workflow at a startup look like? Probably like this: > One founder talks to customers > Another founder builds > A customer asks for something. The first founder explains it to the second. The second founder explains it to Claude > Two weeks any one of the founders asks one of the following questions: \* Why are we building it this way? \* What happened here? \* What did we promise ACME we’d do? \* How far along are we on X? > Then you scream on the inside because you have to figure out what happened... Before agents, the person who did one part of the work…
16d ago · praxos.ai
- 24IL
VSCode was my daily driver for years, but once I started running several coding agents across multiple projects at the same time, it got in the way. One workspace with terminals in the bottom tray, no idea which agent was doing what and I found myself needing all the code editing tools less and less. So I built my own IDE around that workflow. Terminals are a first-class citizen, every project stays alive in the background with visual statuses. Close the workspace and come back weeks later, everything is still in its place. I've been using it for weeks and it's a big productivity boost. The…
Jul 2026 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →