About GEBible

What this is

Most of GEBible is a reader. These are the parts of it:

• 24 translations — every one of them public domain or openly licensed, each with its licence and required credit shown on Sources & licenses, and each of them readable from the book list.
• A chapter reader, side-by-side comparison, and a study page for every verse — each verse has a stable address you can cite, link and come back to.
• Cross-references — the Treasury of Scripture Knowledge lineage, by way of the OpenBible.info dataset. They are topical, not lexical: they link passages by theme and subject, and make no claim that two verses share a word in the original language. They have been re-mapped to this app’s reference scheme and filtered by community vote-weight.
• Commentary — 39 named voices, historical and modern, each quoted verbatim and cited by author and date, never rewritten and never paraphrased here. The full roster, with every voice’s licence and required attribution, is on Commentary sources.
• Search — including an optional “related by meaning” band that ranks passages with a sentence-embedding model run on this site’s own server. Your search is never sent to a third party.
• Topical browse — over public-domain nineteenth-century topical arrangements of the Bible, each of them one editor’s grouping of the text into subjects, cited rather than endorsed. They are at Topics.
• Offline reading — a page you have recently opened stays readable when the connection drops, and Settings carries an opt-in download that saves the current translation’s chapters onto your own device.

What this site adds to the texts

Nearly everything in the section above is other people’s work, republished here under the licences those sources carry. What follows is what this site does with that material, and it is the part that is written here.

Curation, selection and framing. The Scripture Analysis sections — 4 of them live today: Science, Messianic Prophecies, Contradictions and Commandments — are each a curated selection of passages, a structure to present them in, guards on what qualifies, and prose that frames every entry. Where a section draws on a third-party dataset or on published scholarship, that source is named, it is public domain or openly licensed, and it is credited on the page that uses it. The source supplies raw material; the choosing, the ordering, the guards and the framing are this site’s own work. Each section is a reading apparatus over its sources rather than a reprint of any of them. They are gathered at Scripture Analysis, and the method behind each one is on How this is built.

Editorial rules that shape what you see. Four of them, each checkable in one click:

• Commentary is ordered chronologically, earliest first — never “best” or “recommended” first. Ranking commentators would be this site deciding which one you should trust; ordering them by date lets you watch a reading develop instead. Every row of the voice index on a verse study page carries its source’s year, and the years run in ascending order.
• The site never characterises a commentator. The one-line teaser beside each voice in that index is that source’s own opening words, cut on a word boundary. It is never written here, in either direction.
• Both readings, at comparable length, with no verdict. Where two readings of a passage conflict, both are given, in the same register; where a question is genuinely open, the page says so. Contradictions is the easiest place to check that.
• An absence is not a verdict. A passage no section covers has not been examined and cleared. It has not been written up yet.

Apparatus the raw text does not have. Translations set beside each other; the re-mapped, vote-filtered cross-reference web; a citable address for every verse; and the offline download above. None of that exists in the source editions — it is built here.

What it does not add. It writes no scripture and claims no copyright in any public-domain text. It quotes commentary rather than endorsing it, and reaches no verdict of its own. And original-language work — interlinear text, Strong’s numbers, morphology and lexica — is not here at all: that belongs to the sibling app Lemma, which this site links out to.

How the analysis sections are made

Each section is built out by hand: what to include, what to guard against, what order to put it in, and what to say around it. How this is built sets that process out section by section, names every source it rests on, and prints the live size of each corpus as the page loads. It is the page to read if you would rather check the method than take this one’s word for it.

Where everything comes from

Everything GEBible serves is public domain or openly licensed, and the licence and any required credit are always shown. Nothing is served here under a licence this site cannot name.

Two inventories carry the detail, and both are generated from what the site actually serves rather than typed out by hand, so neither can drift out of date. Sources & licenses lists all 24 translations, the cross-reference dataset, the typefaces, the search model and the topical works. Commentary sources lists all 39 commentary voices, each with its licence and the attribution that licence requires. Each Scripture Analysis section carries its own source-and-licence notice on its own page.

What this site does not do

Part of what a reader is owed is what a site declines to do. Each of these is true today:

• No account, and no signup. There is no password and no profile, and nothing here asks you to make one.
• No reading history on any server. There is no user table and no profile, so there is no record of what you read to join together — what the site remembers, it remembers on your own machine, and the privacy policy sets out exactly what and where.
• No analytics, and no tracking scripts of its own. No analytics product, no pixels, no session recording.
• No permanent paywall. Every translation, every commentary voice and every analysis section is free to read at every level.
• No devotional framing. There is no reading plan pushed at you and no page telling you what to feel about what you have just read.
• No verdict on the text. The analysis sections report positions and attribute them to the people who hold them. The site reaches no conclusion of its own, and the terms say so too.

Who makes this

GEBible is built by an independent developer who publishes under the name Godless Engineer and is on Patreon. There is no company here and no investors: it is one person’s project, run in his own time.

I’m an atheist who created GEBible to make the Bible’s contradictions, scientific errors, historical issues, and ethical problems easier to find and examine.

The site takes no position on the text. That is not an assurance, it is a set of rules, and each one is visible on the page it governs. Commentary is ordered by date rather than by preference, so no voice is promoted over another. A commentator’s one-line teaser is that source’s own words, never this site’s. Where two readings conflict, both are given, at comparable length and with no verdict. And a passage that no section covers has not been examined and cleared — it simply has not been written up yet.

I built GEBible because I was tired of seeing discussions about biblical contradictions, scientific issues, and other difficult topics weakened by poor sourcing, exaggeration, or fabricated information. I wanted a deep-study assistant that makes these issues easier to find and examine while reporting what the evidence supports—even when it complicates my own position.

How this is paid for

GEBible is free to read, with no permanent paywall. It carries advertising, and readers can also support it monthly on Patreon — that is optional, and it changes nothing about what the site contains. The levels, and what each one does, are on Support; what an advertisement sets on your device, and how to opt out of personalised advertising, is set out in the privacy policy.

Corrections and contact

Email john@godlessengineering.com. One person, not a ticket system.

That is the address for a typo, a mis-aligned reference, a broken page, a licensing question, or a disagreement with something an analysis page says. If you find an error, tell me and I will fix it. Corrections to the underlying public-domain sources themselves are tracked upstream, with the projects that publish them. What to send where is set out on Contact.