LoreKeeperは、TTRPGのゲームマスターや作家向けのAI搭載アシスタントです。詳細な世界、ルール、NPC、ゲームアセットの作成を支援し、キャンペーンの準備を効率化します。数時間の準備時間を数分に短縮し、インテリジェントでインタラクティブなパートナーと共に創造的なビジョンを実現しましょう。
tryhogwartsは、ファンタジー作家、世界観構築者、RPG愛好家のためのAI搭載クリエイティブスイートです。複雑な魔法体系、魅力的なキャラクターの背景、詳細なファンタジーマップ、分岐するプロットラインを生成します。高度な生成AIの助けを借りて、想像力を解き放ち、あなた自身の魔法の宇宙を構築しましょう。
製品概要
LoreKeeper 製品概要
LoreKeeperは、TTRPGのゲームマスターや作家向けのAI搭載アシスタントです。詳細な世界、ルール、NPC、ゲームアセットの作成を支援し、キャンペーンの準備を効率化します。数時間の準備時間を数分に短縮し、インテリジェントでインタラクティブなパートナーと共に創造的なビジョンを実現しましょう。
tryhogwarts 製品概要
tryhogwartsは、ファンタジー作家、世界観構築者、RPG愛好家のためのAI搭載クリエイティブスイートです。複雑な魔法体系、魅力的なキャラクターの背景、詳細なファンタジーマップ、分岐するプロットラインを生成します。高度な生成AIの助けを借りて、想像力を解き放ち、あなた自身の魔法の宇宙を構築しましょう。
Detailed feature comparison
| Feature | LoreKeeper | tryhogwarts |
|---|---|---|
| 主要カテゴリー | 世界構築 | ストーリーテリング |
| 追加日 | 2025-08-10 | 2025-08-06 |
| 価格 | フリーミアム | フリーミアム |
| 公式サイト | lorekeeper.com | ww25.tryhogwarts.com |
| 製品タイプ | ウェブサイト | ウェブサイト |
| Performance data | ||
| ユーザー評価 | 未確認 | 未確認 |
| コメント | 0 | 0 |
| 月間訪問数 | 6.3K | 3.4K |
| 月間成長率 | 73% | 未確認 |
| お気に入り | 125 | 109 |
| Details | 詳細を見る | 詳細を見る |
LoreKeeper vs tryhogwarts monthly traffic
Compare LoreKeeper and tryhogwarts by monthly reach, traffic trend, visit depth, top regions, and acquisition sources.
How to interpret the traffic data
In the LoreKeeper vs tryhogwarts monthly traffic comparison, LoreKeeper currently shows 6.3K visits and tryhogwarts shows 3.4K; LoreKeeper has about 1.8 times the visible traffic of tryhogwarts, an absolute difference of about 2.9K visits. This reflects visible reach, not feature quality or paid users.
Only LoreKeeper has complete third-party traffic details; tryhogwarts uses visits recorded inside ToolMage. These scopes cannot estimate market share directly, and on-site views should not be treated as the product’s total website traffic.
LoreKeeper monthly traffic:
Latest traffic
Monthly traffic trend
- 2025/9: 4.2K 月間訪問数
- 2026/1: 7.4K 月間訪問数
- 2026/2: 4.4K 月間訪問数
- 2026/3: 4.5K 月間訪問数
- 2026/4: 3.6K 月間訪問数
- 2026/5: 6.3K 月間訪問数
主要地域
Top 5 countries/regions
| Country/region | Percentage | Traffic |
|---|---|---|
| 🇺🇸United States | 59.96% | 3.8K |
| 🇪🇸Spain | 21.95% | 1.4K |
| 🇧🇷Brazil | 16.13% | 1K |
| 🇨🇦Canada | 1% | 63 |
| 🇯🇵Japan | 0.96% | 60 |
流入元
| Source type | Percentage | Traffic |
|---|---|---|
| ダイレクト | 93.34% | 5.8K |
| 参照元 | 6.66% | 417 |
検索キーワード
tryhogwarts monthly traffic:
Latest traffic
Usage comparison
Compare the core capabilities of LoreKeeper and tryhogwarts
LoreKeeper Core features
tryhogwarts Core features
Use cases
LoreKeeper Use cases
tryhogwarts Use cases
LoreKeeper vs tryhogwarts:In-depth comparison and selection guidance
First decide whether the products solve the same kind of need
This in-depth LoreKeeper vs tryhogwarts comparison uses only the product records, taxonomy, audience, traffic, and community signals available on this page. LoreKeeper is primarily listed under “世界構築”, while tryhogwarts is primarily listed under “ストーリーテリング”, so the first decision is whether your actual task matches their recorded scope.
The structured fields currently show these decision-relevant differences: Primary category (LoreKeeper: 世界構築; tryhogwarts: ストーリーテリング); Monthly visits (LoreKeeper: 6.3K; tryhogwarts: 3.4K); Favorites (LoreKeeper: 125; tryhogwarts: 109); Website (LoreKeeper: lorekeeper.com; tryhogwarts: ww25.tryhogwarts.com); Added (LoreKeeper: 2025-08-10; tryhogwarts: 2025-08-06). These facts are more useful for selection than brand visibility alone.
What market visibility and monthly traffic mean
In the LoreKeeper vs tryhogwarts monthly traffic comparison, LoreKeeper currently shows 6.3K visits and tryhogwarts shows 3.4K; LoreKeeper has about 1.8 times the visible traffic of tryhogwarts, an absolute difference of about 2.9K visits. This reflects visible reach, not feature quality or paid users.
Only LoreKeeper has complete third-party traffic details; tryhogwarts uses visits recorded inside ToolMage. These scopes cannot estimate market share directly, and on-site views should not be treated as the product’s total website traffic.
The current traffic scope is not sufficient for a reliable product ranking. Treat monthly visits as a market-interest signal, then decide using taxonomy, use cases, pricing, and a like-for-like trial rather than reading exposure as product capability.
Product positioning, use cases, and roles
LoreKeeper and tryhogwarts currently overlap in shared categories: ライティング; shared tags: キャラクター作成、RPG、ストーリージェネレーター、世界観構築、ライティングアシスタント. This can place both on the same shortlist, but it does not prove equal implementation, depth, or cost.
LoreKeeper's unique categories/tags are 世界構築、ロールプレイング、キャンペーンプランナー、D&D、ダンジョンマスター、ゲームマスター、テーブルトークRPG; tryhogwarts's are ストーリーテリング、画像生成、ゲーム、AIアート、ドラッグ&ドロップ、ファンタジー、ゲーム開発、ナラティブデザイン. These unique fields are the strongest differentiators: validate the product whose recorded scope matches the task instead of following traffic alone.
What ratings, comments, and favorites can tell you
LoreKeeper has no verified rating, 0 comments, 125 favorites, and 114 likes;tryhogwarts has no verified rating, 0 comments, 109 favorites, and 126 likes。
Neither product has enough rating or comment samples for a credible reputation ranking.
Selection guidance by actual need
When to evaluate LoreKeeper first
Put LoreKeeper on the priority trial list when the task aligns with “世界構築” and especially 世界構築、ロールプレイング、キャンペーンプランナー、D&D、ダンジョンマスター、ゲームマスター. This follows recorded positioning and does not imply unlisted capabilities are absent.
LoreKeeper also currently records: pricing is freemium, product type is website, 6.3K verified monthly visits, no verified user rating. Verify any hard requirement around price, platform, or reach before trial, and do not let sparse review data substitute for testing.
When to evaluate tryhogwarts first
Put tryhogwarts on the priority trial list when the task aligns with “ストーリーテリング” and especially ストーリーテリング、画像生成、ゲーム、AIアート、ドラッグ&ドロップ、ファンタジー. This follows recorded positioning and does not imply unlisted capabilities are absent.
tryhogwarts also currently records: pricing is freemium, product type is website, 3.4K on-site monthly views, no verified user rating. Verify any hard requirement around price, platform, or reach before trial, and do not let sparse review data substitute for testing.
How to validate the recommendation before deciding
The available data describes positioning, public visibility, and community signals, but it cannot prove output quality, speed, integration effort, privacy, or long-term cost in your workflow. Before deciding, run the same representative tasks in LoreKeeper and tryhogwarts, then record completion time, accuracy, manual corrections, and the real paid threshold. A like-for-like trial turns this comparison into a defensible adoption decision.




