Comparisons
FTTHelper vs the wikis
FTTHelper keeps player notes private at the database level. The tools below are world wikis. That is a different job.
| Capability | FTTHelper | World Anvil | LegendKeeper | Loreify | Kanka |
|---|---|---|---|---|---|
| Player-private notes enforced at the database row | Yes — Postgres RLS | Article permissions on a wiki page | Document permissions | Page visibility settings | Per-entity visibility setting |
| Player notes become DM hooks, author name stripped | Yes — built-in loop | — | — | — | — |
| Imported/captured content lands hidden until shared | Yes — DM_ONLY by default | Manual per article | Manual per document | Manual per page | Manual per entity |
| Session transcript to canon pipeline | Yes — review-first ingest | — | — | — | — |
Competitor cells describe each tool’s documented permission model at the category level, not a claim about internals.
- FTTHelper vs World Anvil
FTTHelper keeps player notes private at the database level. World Anvil is a world encyclopedia with article permissions.
- FTTHelper vs LegendKeeper
FTTHelper is a campaign workspace with spoiler-safe subjects. LegendKeeper is a mapping-first wiki.
- FTTHelper vs Loreify
FTTHelper has a player-notes-to-hooks loop no wiki has: private desire notes become DM hooks with the author name stripped.