GitHub’s Arctic Code Vault and Future Glass Storage for Open Source Code
GitHub’s Arctic Code Vault initiative has archived millions of open‑source projects on film stored in a Norwegian Arctic facility, and the company now plans to preserve code for millennia using quartz glass through Microsoft’s Project Silica, highlighting long‑term data preservation strategies for software.
GitHub announced that all open‑source contributions made before February 2 have been packaged and sent to the Arctic as part of the Arctic Code Vault, a project aimed at preserving code for a thousand years.
Millions of programs have already been contributed to the vault, and GitHub introduced honor badges that appear on developers’ profiles when their projects are stored in the Arctic.
The code was transferred to the Norwegian data‑preservation company Piql, where 21 TB of source code were written onto 186 film reels; each frame contains about 8.8 million pixels and the source code is encoded as QR codes.
These reels were shipped to Oslo, flown to the Svalbard archipelago, and stored in an underground facility at Longyearbyen, located in a former coal mine that also houses the Global Seed Vault, providing a stable, cold environment for long‑term preservation.
Looking ahead, GitHub is exploring glass‑based storage through Microsoft’s Project Silica, which uses laser‑etched quartz glass capable of lasting tens of thousands of years; the initiative has already archived 6,000 of the world’s most popular open‑source repositories.
The community reacted with humor, noting that their bugs will now be immortal, while emphasizing the significance of these long‑term preservation technologies.
DevOps
Share premium content and events on trends, applications, and practices in development efficiency, AI and related technologies. The IDCF International DevOps Coach Federation trains end‑to‑end development‑efficiency talent, linking high‑performance organizations and individuals to achieve excellence.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.