Hi HN. I'm the developer (and a pastor). This project was born out of my own frustration.

I'm a $43k-level power-user of Logos Bible Software, but I was still spending 10-20 hours a week on the exegetical work—collating word studies, parsing Greek/Hebrew, and comparing parallels for my sermons. I built the tool I wished I had.

The result is the Anselm Project. It's two parts:

The Engine (Free): A 200M+ token generative database of the entire 66-book Bible. It uses LLMs to generate a full scholarly apparatus (morphology, parallels, and in-progress text-crit) for every verse. You can browse this for free. There's no login needed for this part.

The SaaS (Paid): A report generator on top. It synthesizes all that data into 40-page sermon prep reports or 60-page academic briefs. I'm a solo dev, not a marketer. I'd also love to retire someday. Ministry doesn't pay much.

The tech: The 200M+ token dataset was generated via API calls in a massive batch process. My cost per academic report is about $0.07. I'm a solo dev, not a marketer.

The free generative Bible is open for browsing. I'd love your feedback on the tech, the model's output, and the (likely buggy) UI. Happy to answer any questions about the data generation, costs, or the tech stack.

Thanks.

My friend, I signed up, and looks like the passage validator is too strict on Bible refs, so I can't generate a report. It rejects smart quotes, en dashes, semicolons, and abbreviations, and seems to require full book names, ASCII hyphens, and comma-separated refs in one line. The format examples also seemed inconsistent.

Are they matching against a simple regex?