About
The team behind zero-breakage updates
We build the tool we wished existed — automated dependency updates that actually fix breaking changes.
Our story
Why Ovvoc exists
Every developer knows the feeling. You open a project after a few months and everything is outdated. Security vulnerabilities pile up. Breaking changes lurk in every major version bump. You run Dependabot, get 47 PRs, and half of them break the build. The other half are version bumps you could have done yourself.
We looked at the landscape and saw a gap. Existing tools solve the easy 70% — version bumps, lockfile updates, things that don't touch your code. But the hard 30%? Breaking API changes, deprecated method replacements, paradigm shifts across frameworks? That gets dumped back on developers. That's where the real pain is, and that's the gap we set out to close.
Ovvoc handles all 25 update categories. It clones your repo, parses the AST, applies deterministic transforms where possible, uses AI narrowly where it can't, builds, tests, and only opens a PR when everything passes. If something fails, you get a detailed report — never a broken branch.
What drives us
Built on principles
Zero-breakage guarantee
If tests fail, we report. We never push broken code. Your main branch is sacred.
Security-first
Ephemeral containers. No persistent code. Self-hosted agent option. Minimum permissions.
Transparency
Detailed failure reports. Confidence scores on every PR. Full audit trail.
Automation over manual
14+ hours per sprint spent on dependency triage. We make that zero.
Engineering
How it's built
Rust backend
Memory-safe, zero-cost abstractions. Every pipeline stage runs in pure Rust for speed and reliability.
OXC AST parser
The fastest JavaScript/TypeScript parser. Real syntax tree transforms, not regex string replacement.
Ephemeral containers
Every job runs in an isolated Docker container. Destroyed after completion. Your code never persists.
Update categories
Migration rules
Packages covered
Pipeline stages