We launched AfterMerge 2 weeks ago. Here’s what we’re questioning already.
When we started building AfterMerge, we thought the obvious workflow was:
PR comes in → AI reviews it → team merges it.
But the more repositories and engineering workflows we look at, the more we think the bigger problem might not start with the PR.
A lot of important issues already exist in a codebase. They aren't raised in a PR. They sit quietly across services, modules, dependencies, and data flows until one day they become an incident.
So we're exploring a new direction:
What if AfterMerge continuously understood your codebase and proactively found potential bugs, security issues, risky code paths, architectural problems, and cross-repository issues?
And we're also debating something bigger:
Should we open-source AfterMerge?
The idea would be to let teams self-host AfterMerge inside their own infrastructure, while we continue offering a fully managed cloud version for teams that don't want to operate it themselves.
For a product that deeply analyzes your source code, self-hosting feels important.
But we're curious:
Would you rather self-host a tool like this?
Would open source make you more likely to try AfterMerge?
What is the first problem you'd want an AI system continuously analyzing your codebase to find?
Would genuinely love your opinion.
Replies