HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
attic-labs
noms
Go2016–2025
attic-labs / noms · Archived

noms

The versioned, forkable, syncable database

33Distinct people
59Mentions
2Explicit recommenders
7.4KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

The versioned, forkable, syncable database

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

Not much more to say other than Noms was my favorite project (https://github.com/attic-labs/noms) for a while until acquisition and the engineers are now the ones behind…

cdbattags used a recommendation phrase. 2 indexed comments match. This is a phrase match, not a verdict.

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

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 5:58:53 AM 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 year59 dated mentions

Observed mentions: 2016-08-02 16:35:18 UTC to 2025-07-01 01:04:44 UTC.

05101520252016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 24 mentions; 2 submissions, 22 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 5 mentions; 0 submissions, 5 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 6 mentions; 1 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 10 mentions; 0 submissions, 10 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025

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
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC24222
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC505
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC615
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC10010
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC606
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC202
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
Warning - This project is not active Noms is not being maintained. You shouldn't use it, except maybe for fun or research. If you are interested in something like Noms, you probably want Dolt (https://github.com/dolthub/dolt) which is a fork of this project and actively maintained. Send me (aaron at aaronboodman.com) a message if you have questions. Use Cases  |  Setup  |  Status  |  Documentation  |  Contact Welcome Noms is a decentralized database philosophically descendant from the Git version control system. Like Git, Noms is: Versioned: By default, all previous versions of the database are retained. You can trivially track how the database evolved to its current state, easily and efficiently compare any two versions, or even rewind and branch from any previous version. Synchronizable: Instances of a single Noms database can be disconnected from each other for any amount of time, then later reconcile their changes efficiently and correctly. Unlike Git, Noms is a database, so it also: Primarily stores structured data, not files and directories (see: the Noms type system) Scales well to large amounts of data and concurrent clients Supports atomic transactions (a single instance of Noms is CP, but Noms is typically run in production backed by S3, in which case it is "effectively CA") Supports efficient indexes (see: Noms prolly-trees) Features a flexible query model (see: GraphQL) A Noms database can reside within a file system or in the cloud: The (built-in) NBS ChunkStore implementation provides two back-ends which provide persistence for Noms databases: one for storage in a file system and one for storage in an S3 bucket. Finally, because Noms is content-addressed, it yields a very pleasant programming model. Working with Noms is declarative. You don't INSERT new data, UPDATE existing data, or DELETE old data. You simply declare what the data ought to be right now. If you commit the same data twice, it will be deduplicated because of content-addressing. If you commit almost the same data, only the part that is different will be written. Use Cases Decentralization Because Noms is very good at sync, it makes a decent basis for rich, collaborative, fully-decentralized applications. Mobile Offline-First Database Embed Noms into mobile applications, making it easier to build offline-first, fully synchronizing mobile applications. Install Download the latest release: Linux Mac OS Unzip the directory somewhere and add it to your $PATH Verify Noms is installed correctly: $ noms version format version: 7.18 built from <developer build> Run Import some data: go install github.com/attic-labs/noms/samples/go/csv/csv-import curl 'https://data.cityofnewyork.us/api/views/kku6-nxdu/rows.csv?accessType=DOWNLOAD' > /tmp/data.csv csv-import /tmp/data.csv /tmp/noms::nycdemo Explore: noms show /tmp/noms::nycdemo Should show: struct Commit { meta: struct Meta { date: "2017-09-19T19:33:01Z", inputFile: "/tmp/data.csv", }, parents: set {}, value: [ // 236 items struct Row { countAmericanIndian: "0", countAsianNonHispanic: "3", countBlackNonHispanic: "21", countCitizenStatusTotal: "44", countCitizenStatusUnknown: "0", countEthnicityTotal: "44", ... Status Nobody is working on this right now. You shouldn't rely on it unless you're willing to take over development yourself. Major Open Issues These are the major things you'd probably want to fix before relying on this for most systems. Sync performance with long commit chains (#2233) Migration (#3363) Garbage Collection (#3374) Query language We started trying to hack in GraphQL but it's incomplete and maybe not the right thing. See: ngql Various other smaller bugs and improvements Learn More About Noms For the decentralized web: The Decentralized Database Learn the basics: Technical Overview Tour the CLI: Command-Line Interface Tour Tour the Go API: Go SDK Tour Contact Us Interested in using Noms? Awesome! We would be happy to work with you to help understand whether Noms is a fit for your problem. Reach out at: Mailing List Twitter Licensing Noms is open source software, licensed by Attic Labs, Inc. under the Apache License, Version 2.0.
Read the full README on GitHub

What Hacker News says

6 sources
There are purpose-built databases for this purpose such as Dolt (https://www.dolthub.com/), itself purportedly derived from noms (https://github.com/attic-labs/noms). Because it's baked into the database, you can do complex things like diffs and merges, but it requires that you run everything on that RDBMS vs. something standard. Generic diffing from two arbitrary data states of any database is pretty challenging, even if you have all the transaction history.
In Show HN: Version Control for Databases
Several interesting open source projects are working with CRDTs to make state synchronization in distributed systems an easier problem to deal with: - Braid HTTP (https://braid.news/) - Automerge (https://github.com/automerge/automerge) - Gun (https://gun.eco/) - Yjs (http://y-js.org/) - Noms (https://github.com/attic-labs/noms) - DAT (https://dat.foundation/) Personally, I'm most excited for Braid's effort to bring state sync to HTTP through the IETF process, as well as Automerge's progress in P2P via Hypermerge (and it's star app, Pushpin). I'd also like to see Gun succeed, but have had a hard time getting started due to visually distracting quirks in its documentation.
In CRDT: Conflict-free replicated data type
Congratulations to the Quilt team on the launch! Quilt reached out to me and suggested I chime in suggesting that people interested in versioning data also check out Dolt (https://github.com/liquidata-inc/dolt) and DoltHub (https://www.dolthub.com). We've taken the Git and GitHub for data analogy a lot more literally than Quilt has :-) We are a SQL database with native Git semantics. Instead of versioning files like Git, we version table rows. This allows for diff and conflict detection down to the cell level. We are built on top of another open source project called Noms (https://github.com/attic-labs/noms). We think there is a ton of room in this space for a bunch of tools: Quilt, Noms, QRI (https://qri.io/), Pachyderm (https://www.pachyderm.io/), and even Git. We're excited to see so many bright minds trying to solve this problem. We'r
Read the rest
e going to be populating DoltHub with a bunch of datasets we harvest from the open data community to show off the capabilities of Dolt. The coolest one so far is the Google open images dataset: https://www.dolthub.com/repositories/Liquidata/open-images.
In Launch HN: Quilt (YC W16) – A versioned data portal for S3
Sirix sounds like a very interesting system! Is it similar in its internal structure to noms (https://github.com/attic-labs/noms) or Dolt (https://github.com/liquidata-inc/dolt)? I think S3 is a good match for storing database pages as long as they are immutable. The Vectorized query processing model seems to fit this approach very well (e.g., http://oai.cwi.nl/oai/asset/14075/14075B.pdf) Anyone out there from Snowflake care to answer how Snowflake stores database pages in AWS? I haven't used BookKeeper or Pulsar myself so I can't comment on how well they might work for distributing an intent log.
In Launch HN: Quilt (YC W16) – A versioned data portal for S3
> Im not sure people really understand the implications of a team of companies that collaborate often banding together, and eliminating the need for 3rd party audits and 3rd party fund settlement. I think it is more that people don't understand what existing technologies there are already, but they've heard of this "blockchain" thing, and the black and white view is one where you either need a blockchain or you don't need anything. There are some other interesting technologies and research areas. One example is SMPC. In 2008 (pre-dating Bitcoin), a secure auction with sealed bids was conducted in Denmark for the purchase of beets from independent farmers[1]. This kind of research get drowned out by the blockchain hype because nobody is interested in something which doesn't print their own money. There are also more well understood distrib
Read the rest
uted databases and consensus algorithms which work when you have semi-cooperative parties. I think a lot of these "blockchains" really just want a merkle-tree, and they could probably get by with a database like noms[2] When you have a bunch of cooperating parties, they either need to assume that the parties are cooperative, or you need an arbitration process. The arbitration process is what the blockchain is about (with the record keeping in the blockchain being a kind of toxic waste which is kept around to support that). What do you do when the parties are being uncooperative? If there are only a few parties, then PoW is not a viable solution because one party could outpace others if they have more computing power. If you pick something like Proof-of-stake, then several parties could collude to swindle others. If you have a centralized system, you've not gained anything. Ultimately, the companies involved are always going to take any quarrels to a legal court and have a human decide the outcome - meaning their blockchain is going to have to be "fixed" by manual intervention anyway. [1]:https://eprint.iacr.org/2008/068 [2]: https://github.com/attic-labs/noms
In JP Morgan Unveils USD-Backed Cryptocurrency for B2B Payments

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.