About

Why

Reading Scripture verse by verse is the right way to read it. But a great deal of what is in the Bible is relationship — this passage answering that one, this person standing in that line, this event happening at that place — and a page of text cannot show you the shape of it. That shape is what this site tries to make visible.

The name comes from John 15. A vine is a network: one stem, many branches, all connected. It seemed a better description of Scripture than anything from graph theory.

How it is built

The text is the Berean Standard Bible, which is in the public domain — the wording and also the way it is set, since the paragraphs, poetry lines, section headings, translator footnotes and the words of Christ are all recovered from the same translation’s typesetting edition rather than guessed at.

Everything around the text comes from openly licensed scholarship, and there is more of it than the text itself:

• BibleData — the people and their families, their Hebrew and Greek names, the 613 commandments, Strong’s Hebrew lexicon, the dated epochs, and the topical themes.
• OpenBible.info — the cross references, and the coordinates and competing site identifications behind every place.
• Clear Bible — who is speaking, which is how the site knows a quotation from its narration.
• Theographic — the 450 narrative events, and the order in which they happen.

Each is credited as its licence requires on the attribution page. Most of what results is CC BY 4.0; the events are CC BY-SA 4.0, which is viral, so they are quarantined in a separate partition that the rest of the corpus never depends on.

The whole thing is generated mechanically from those sources into Open Knowledge Format documents — plain markdown you could read without any of this. Nothing here was written by a language model, and nothing has been reviewed by a person, so every document is marked accordingly.

What it does not claim

• Cross references carry no meaning. The corpus records that two passages are connected, never why. Where the data does not say, neither does this site.
• Where scholars disagree, both are shown. 777 biblical places have more than one proposed modern location; each is listed with its support rather than resolved to a single answer.
• Some of the data is interpretation, and this is where. The topical themes are Nave’s groupings from 1897; the epoch dates are Ussher’s seventeenth-century chronology, counted in years from Creation; the 613 commandments follow the traditional Jewish enumeration, with its Mishneh Torah and Sefer HaChinuch cross-references. Each is one scholarly frame rather than a consensus, and it is reproduced here because the source records it — not because the site endorses it.
• Nothing is interpreted for you. Beyond what those sources bring, there is no commentary here and no theological position of ours.

Known gaps

• Nobody has read any of it. No document has been reviewed by a person, so every trust signal in the data is a mechanical check and nothing better.
• Chapter summaries have not been written. They are the one part of this that would need a language model, and none has been run, so no chapter claims a summary it does not have.
• The lexicon is Hebrew only. Strong’s Greek numbers are recorded throughout but link nowhere, because this bundle carries no Greek lexicon — and the Hebrew side holds the words behind biblical names and their roots rather than all of Strong’s.
• A name’s meaning is about the name, not the person. Around 2,300 people carry a gloss from Hitchcock’s dictionary, and it is keyed to the name alone — all twenty-three Zechariahs get the same one. It is attributed and phrased that way throughout rather than folded into anyone’s description.
• The event graph joins imperfectly. 245 people and 43 places named in the events match nothing in the permissive datasets, so those events carry fewer links than the rest. The join refuses an ambiguous match rather than guessing one.
• 56 verses are set as plain paragraphs. The two editions of the Berean disagree about their wording, and a word offset computed against one is meaningless against the other, so those verses lose their poetry and paragraph breaks. They are named individually in the changelog.

It is free, carries no advertising and tracks nothing about you. If it is useful, you can help keep it online.