Unison is an automated code-maintenance platform that detects API changes and proactively updates customer codebases to prevent breaking changes. It monitors API specifications, SDKs, and documentation, identifies affected repositories, generates repository-specific migrations, runs tests in isolated sandboxes, opens pull requests, and monitors CI. Humans are involved only when a migration is ambiguous or fails verification. Our initial form factor is a GitHub app.
We built Unison after noticing a frustrating gap in how software maintenance works today.
When an API or SDK changes, the downstream work is still surprisingly manual. Someone has to notice the change, figure out which code is affected, read the migration docs, make the changes, run tests, and open a PR.
We kept asking: why should an engineer have to initiate this process at all?
Unison continuously monitors the APIs and SDKs your code depends on. When something changes, it identifies the affected code, generates the migration, validates it with tests, and prepares a production-ready PR for review.
The goal is simple: APIs change. Your code keeps up.
We’re a three-person founding team with backgrounds spanning AI research at UMass Amherst, including a recent EMNLP 2026 publication; software engineering at Apple and IIT Kharagpur; and Stanford, with prior startup experience scaling to $60K ARR.
We’re still early and would especially love feedback from engineers who maintain third-party integrations. How does your team handle API/SDK changes today, and what would Unison need to get right for you to trust it with this work?
If Unison sounds useful for your team, you can join the waitlist on our website. We’d love to have you along as we build it.
Hey Product Hunt! 👋
We built Unison after noticing a frustrating gap in how software maintenance works today.
When an API or SDK changes, the downstream work is still surprisingly manual. Someone has to notice the change, figure out which code is affected, read the migration docs, make the changes, run tests, and open a PR.
We kept asking: why should an engineer have to initiate this process at all?
Unison continuously monitors the APIs and SDKs your code depends on. When something changes, it identifies the affected code, generates the migration, validates it with tests, and prepares a production-ready PR for review.
The goal is simple: APIs change. Your code keeps up.
We’re a three-person founding team with backgrounds spanning AI research at UMass Amherst, including a recent EMNLP 2026 publication; software engineering at Apple and IIT Kharagpur; and Stanford, with prior startup experience scaling to $60K ARR.
We’re still early and would especially love feedback from engineers who maintain third-party integrations. How does your team handle API/SDK changes today, and what would Unison need to get right for you to trust it with this work?
If Unison sounds useful for your team, you can join the waitlist on our website. We’d love to have you along as we build it.
Thanks for checking us out! 🚀