Access trustworthy and openly-licensed Bible content in multiple languages through the Aquifer Github repositories.
In nature, aquifers are filled with fresh water. In the global church, there is a need for an Aquifer of another kind - one filled with trustworthy, openly licensed, unrestricted Bible resources for global translation organizations. The Aquifer on Github enables the development of Bible translation apps and other biblical resources in many more languages. With Aquifer Bible resources available on Github in an open source digital content library, the acceleration of high quality Bible translations for all nations, people and languages can be achieved.
Aquifer resources are available on Github in resource repositories, like the one for the Aquifer Open Study Notes. The repository contains all available languages of the resource. If you don't want to clone the repository (the Github method of retrieving the repository for use on your local computer) you can just grab the languages you'd like from the latest resource release. Check out all of the resource repositories we have available for download.
We are working on making all of the content from the Aquifer — Bibles, Dictionaries, Study Notes, Audio, etc. — available here for easy access. But it is not all here yet. We have started with all of the resources that are not Bibles. That includes Dictionaries like the Aquifer Open Bible Dictionary, study notes like the Biblica Study Notes, and translation guides like the Fia Translation Guides and the unfoldingWord Translation Notes.
Bibles, audio Bibles, and Bible alignments will be available in the coming weeks and months.
If you're looking to implement these resources in your organization's applications or other tooling, that's awesome! We have some documentation available that we plan on expanding. Resources follow a date-based versioning scheme (with tags like v2025-10-28) which are used to generate releases (like these releases for the Aquifer Open Bible Dictionary). All of our resource JSON is validated against our schemas — which also provide a Scripture Burrito-esque form of metadata for processors that are familiar with that vocabulary.
