They say all good things must come to an end, and certainly we’ve seen it before with open source projects. But sometimes, it’s not the end, just time to enter a new season! I’m so happy to report the latter for DVC! We are excited for DVC to find a home with lakeFS!
We know you may have questions on this transition, and I’ve put together this FAQ post to do just that. For a farewell message from Dmitry Petrov, please take a look at his blog post here.
1. What’s happening?
lakeFS has acquired the DVC open-source project from Iterative.ai.
This means lakeFS will now take over stewardship and active development of DVC. DVC remains an open-source project with its own community and website (dvc.org), while benefiting from lakeFS’s resources and long-term commitment to open source data version control.
2. How will this affect the projects I have that use DVC?
There will be no change, other than the knowledge that DVC will be maintained into the future by a company equally committed to data version control and best practices in AI/ML!
For those using the DVC extension for VS Code, some adjustments will need to be made over time to transfer the extension to Treeverse. When the full switch occurs, you will need to reinstall the extension from Treeverse. Once this is done, everything will work as before. We will keep you in the know about the changes. Be sure to subscribe to our email if you have not already.
3. Will my existing projects or workflows break?
No. There are no breaking changes to DVC behavior, commands, or existing workflows.
Your projects will continue to run exactly as before. Future updates will remain backward-compatible.
4. Why did this happen?
Iterative built DVC into one of the most widely used tools in data science. Over the years, Iterative’s focus shifted to the multimodal AI world. lakeFS and DVC have always been congenial, not competitors:
- DVC helps individual data scientists and small teams manage data, model, and experiment versioning easily.
- lakeFS supports enterprise-grade version control for petabyte-scale data lakes.
By joining forces, we’re amplifying the data version control space. DVC can continue to grow while expanding what’s possible for users across all scales—from personal projects to enterprise AI platforms.
5. Is DVC still open source?
Yes. Absolutely.
DVC will remain 100% open source under the same license. There are no plans to change licensing, paywall features, or restrict access.
lakeFS’s team is committed to open source and has its own open source version of lakeFS, and will continue DVC’s public development on GitHub.
6. Will DVC still be maintained and developed?
Yes. lakeFS is committed to keeping DVC, DVCLive and the DVC extension for VS Code alive, maintained, and evolving. The engineering team has already made that transition and taken on DVC’s codebase to ensure continuity. Expect to see ongoing maintenance, bug fixes, and compatibility updates!
7. What happens to the DVC website, docs, and community channels?
All existing DVC resources stay as they are with the exception of the repos which will move under Treeverse’s main repo:
- Website: dvc.org
- Docs: doc.dvc.org and redirected dvc.org/doc
- Blog: dvc.org/blog
- GitHub: All repos below will be transferred from the Iterative repo to the Treeverse repo in the coming months
- DVC repo: Eventually to github.com/treeverse/dvc (ownership may change to lakeFS org, but repo and history remain)
- DVC.org repo: Eventually to github.com/treeverse/dvc.org
- Project repos: Those repos attached to projects in the DVC Docs, on the DVC blog, DVC online course will still be available and ultimately transferred the Treeverse repo.
Discord, Discuss, YouTube, and social channels: continue as before, with the exception of LinkedIn. Please follow DVC on our LinkedIn page.
8. Will DVC be merged into lakeFS or remain separate?
DVC will remain its own project and brand for the foreseeable future.
The two products serve different audiences and use cases:
- DVC: lightweight Git-based tool for small-to-medium data science projects
- lakeFS: scalable infrastructure for enterprise AI and data platforms
9. How does this benefit DVC users directly?
- Continued maintenance and longevity for the DVC project
- Access to new resources from lakeFS
- Broader community and knowledge sharing with enterprise practitioners
- No cost changes or usage restrictions
10. Will the DVC team or roadmap change?
The roadmap will evolve with input from both communities. lakeFS’s engineering and product teams will maintain DVC with an open roadmap and community discussions, just like before.
Community feedback will continue to drive priorities as it always has.
11. Who should I contact if I have questions or concerns?
You can reach out directly via:
- Discord: https://discordapp.com/invite/dvwXA2N
- Community forum: discuss.dvc.org
- Email: support@dvc.org
Please use the email above to contact me with any questions!
Join our Webinar: A New Chapter for DVC: Passing the Torch to lakeFS
We are having a webinar on December 3, 2025 with Dmitry Petrov and Oz Katz from lakeFS to discuss the transition. We look forward to seeing you there!
📰 Join our Newsletter to stay up to date with news and contributions from the Community!