Home › About
PuzzleBindery is made by one person — Rolf Eriksen — and this page says who that is, how the puzzles are actually produced, and what the software does and does not do.
I built PuzzleBindery to publish my own puzzle books without paying another monthly subscription. The tools I looked at were priced as research platforms — keyword data, niche analysis, template libraries — and I was using one feature of them. Paying per year, indefinitely for a generator felt like the wrong shape for the job, so I wrote one.
That is also why it is a one-time purchase rather than a subscription. It is a tool you buy, not a service you rent.
Every puzzle is generated by deterministic code running in your browser — not written by hand, and not produced by a language model. A puzzle is defined by its type, a random seed and its parameters, and the grid is rebuilt from that recipe whenever it is drawn. Two consequences worth knowing:
Where a language model is involved it is clearly bounded: the optional custom-theme feature asks one to suggest a word list for a topic you type. It drafts vocabulary only. Grid placement, uniqueness, difficulty, margins and layout are all deterministic code, and every suggested word is validated against the same rules the hand-curated themes obey before it can be used.
It has no keyword or niche research, no Amazon sales data, and no templates for journals, planners or logbooks. It makes puzzle book interiors and their covers. If you need the research half, you will need something else alongside it — there is a longer comparison that says so in more detail.
Support email goes to me. There is no team and no ticketing system, so replies are not instant, but they are from the person who wrote the code. Bug reports are genuinely welcome and usually get fixed quickly.
Contact: [email protected] — see the contact page for what to include in a bug report.