HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Oxen-AI
Oxen
Rust2023–2026
Oxen-AI / Oxen

Oxen

Lightning fast data version control system for large repositories of data. Feels like git, pushes and pulls like oxen.

10Distinct people
30Mentions
0Explicit recommenders
1.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Lightning fast data version control system for large repositories of data. Feels like git, pushes and pulls like oxen.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year30 dated mentions

Observed mentions: 2023-01-20 22:44:26 UTC to 2026-07-19 17:10:31 UTC.

0510152023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 17 mentions; 2 submissions, 15 comments20232024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments20242025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC17215
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC312
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC505
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC505

What Hacker News says

30 sources
I do think git serves a lot of people's needs very well. I see a lot of people being quite happy with direct github alternatives. Self hosting may become more popular too, I hadn't heard too many self hosting stories until recently. If LFS is your pain (I cannot stand to use git lfs) I have to mention oxen, which is open source and self hostable, but also has a hosted option. It handles large files right out of the gate and doing so faster than everyone else is one of its core missions. Still using github for distribution though, lol, see https://github.com/Oxen-AI/Oxen. I am also curious about where jj will go, its philosophy is really interesing, and sounds promising.
In Why developers are ditching GitHub for Codeberg and self-hosting alternatives
The premise is that Git-LFS sucks, so we need to build a new data versioning system (in Rust, from scratch). While I mostly agree with this premise, but there are already lots of existing (mature) data versioning systems with the same tricks under the hood: - Pachyderm (Go): https://github.com/pachyderm/pachyderm - XetHub (acquired by HuggingFace): https://huggingface.co/blog/xethub-joins-hf - LakeFS (Go): https://github.com/treeverse/lakeFS - Oxen (Rust): https://github.com/Oxen-AI/Oxen I guess with AI, anyone can vibe code a content-addressed, chunk-level deduped, versioning system in Rust these days... But jokes aside, Lore seems really cool! What's interesting is the realization that different domains/industries have similar problems, but they don't seem to be cross-polinating. In this case AI and Gaming both need a storage system th
Read the rest
at can version control large binary files at scale. I think there's lots of opportunities to share ideas here, but perhaps the lack of idea sharing (currently) creates opportunity!
In Lore – Open source version control system designed for scalability
One of the maintainers of the Open Source project "Oxen" here. Our VCS scales for binary data better than git does, and was built to solve some of the problems with git-lfs and git-annex. We've had a few requests to integrate with music production workflows, but haven't taken it on yet. If anyone wants to collaborate to integrate Oxen with their DAW or workflow let us know! Here's the project: https://github.com/Oxen-AI/Oxen
In Git for Music – Using Version Control for Music Production (2023)
We're working on Oxen.ai which is an Open Source CLI and Server with Python bindings as well. Optimized for ML/AI workloads but works with any type of data and we see usage from game companies, bio, aerospace etc. Feel free to check it out here: https://github.com/Oxen-AI/oxen-release Or a hub you can host data on (we have public and private repos, or private VPC deployments): https://oxen.ai The CLI mirrors git so it's easy to learn. It has some interesting build in tooling for diff-ing datasets and working on them remotely without downloading a full copy of the data as well. Happy to answer any other questions!
In Ask HN: How do you version your data?

Show HN: Oxen.ai – Data Diff tool to quickly find changes in CSV, parquet, etc.

Hey all, We added a recently added a data diff tool to the Oxen.ai toolchain. Feel free to checkout the docs here: https://docs.oxen.ai/concepts/diffs If you aren’t familiar with Oxen.ai we are building dataset version control optimized for structured datasets of csvs, jsonl, parquet files, etc as well as multimodal datasets of images, audio, video, text, etc. We wanted add a tool to the toolchain that could quickly narrow down schema changes as well as find added/removed/modified rows in data frames. The hope is that this will be a more powerful tool than a git diff when it comes to iterating on datasets. With data you are no longer scanning line by line to verify changes - but dealing with data distributions and data frames. You can pipe these diffs into any data analysis tool (pandas, polars, your custom Jupyter notebook) and quickly g
Read the rest
et to the crux of what changed. Let us know if this type of tool would be helpful in your workflow! The github can be found here: https://github.com/Oxen-AI/oxen-release
4 points · Open discussion
We've been working on a data version control system called "oxen" optimized for large unstructured datasets that we are seeing more and more with the advent of many of the generative AI techniques. Many of these datasets have many many images, videos, audio files, text as well as structured tabular datasets that git or git-lfs just falls flat on. Would love anyone to kick the tires on it and let us know what you think: https://github.com/Oxen-AI/oxen-release The commands are mirrored after git so it is easy to learn, but optimized under the hood for larger datasets.
In Ask HN: Can we do better than Git for version control?
We have been working on an open source tool called "Oxen" that aims to tackle this problem! Would love for you to kick the tires and see if it works for your use case. We have a free version of the CLI, python library, and server on github, and a free hosted version you can kick around at Oxen.ai. Website: https://oxen.ai Dev Docs: https://docs.oxen.ai GitHub: https://github.com/Oxen-AI/oxen-release Feel free to reach out on the repo issues if you run into anything!
In Ask HN: How do your ML teams version datasets and models?

Showing the 15 most recent of 30 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.