Honest comparison
Foreverse vs StoryLord
StoryLord (gennovel.app) overlaps with Foreverse more than anything else on this list: upload TXT/DOCX/Markdown or pick a public-domain classic, steer the AI's continuation or rewrite, publish the result to a community library — 100 free credits at signup, one-time packs after. Which model writes for you is not disclosed as of 2026-07. Foreverse is the on-device answer: a native Android reader, 62 providers on your keys, and continuations that grow as branches beside the original, never over it.
| Dimension | Foreverse | StoryLord |
|---|---|---|
| Getting started | Install the app, import a book, add a key (~10 minutes) | Sign up in a browser, 100 free credits, start directing chapters |
| Source material | On-device txt/epub import (315 books tested on real hardware) | TXT/DOCX/Markdown upload with encoding detection, or a built-in public-domain library |
| Output vs the original | Continuations land on branches beside the untouched original; parallel timelines coexist | AI chapters read continuously after the original; how rewrites preserve the source is not publicly documented (as of 2026-07) |
| Model transparency | 62 providers via your keys, switchable per scene | Platform model; no model names or picker found on the site (as of 2026-07) |
| What is free | Core app free, no message caps; 5,000-credit signup grant on the official channel (~260 continuations) | 100 credits at signup, then one-time packs ($9.99/1,500 · $13.99/3,000) |
| Writing languages | Prose follows the model you bring; UI is Chinese-first, English localized and still being polished | 9 writing languages supported explicitly |
| Publishing & community | Community card site, still small; publishing entirely optional | One-tap publish to a community library of AI-enhanced novels |
| Platform | Native Android app on Google Play (iOS in beta signup); reads offline, narrates on lock screen | Web product in any browser; no native app found (as of 2026-07) |
| Data custody | Books and branches are local files, exportable as a bundle | Manuscripts and chapters live in the platform account |
The overlap is real — down to Chinese-encoding detection
Most products on this page compete with one corner of Foreverse. StoryLord competes with the middle of it. Upload a manuscript in TXT, DOCX, or Markdown — the site detects encodings automatically, Chinese novels included — or pick a public-domain classic from its built-in library. Tell the AI where the story should go, approve a chapter-by-chapter outline, and read the new chapters in an interface that stitches original and AI chapters into one continuous read. The billing is refreshingly un-subscription: 100 credits free at signup, then one-time packs at $9.99 for 1,500 or $13.99 for 3,000. The outline-first workflow is a real quality gate, and the one-tap publish to its community library is something we simply do not offer.
What the site does not say matters to a BYOK audience. Nowhere could we find which model writes your chapters, or a way to choose one (as of 2026-07). Your manuscript and everything generated from it live in the platform's account system, reachable through a browser. None of that is sinister — it is the standard shape of a web product — but it is the exact set of trade-offs Foreverse was built to refuse.
Who knows which model wrote your chapter?
With Foreverse the answer is: you, because you picked it. Keys stay encrypted on your device and calls go straight to the provider at list price — 62 presets plus any OpenAI-compatible endpoint — or you use the official metered channel (1 credit = $0.0001, 5,000 granted at signup, roughly 260 continuations). Swap the model per scene: a cheap fast one for filler chapters, a frontier one for the confrontation the whole book was building toward.
The other structural difference is where the words land. StoryLord's new chapters read continuously after the original — good for a finished product you publish. Foreverse assumes you will change your mind: select any passage mid-read, continue from there, and the result grows as a branch beside the original text, which never moves. Keep three endings side by side; discard none of them. And because books are local files, the whole library reads offline and narrates on the lock screen — things a browser tab cannot promise.
Pick StoryLord if
- You want to publish your continuation for others to read — its community library has no equivalent here
- You want a browser tab that works right now, on any OS, with zero setup
- You write in one of its 9 supported languages and want that handled explicitly rather than by your model choice
Pick Foreverse if
- Your novel is already on your phone: import the txt/epub and keep reading offline
- You want continuations as branches beside the original, never over it — parallel timelines you can compare and roll back
- You want to know and choose the model: 62 providers on your keys at list price, or official metered credits
- You are keeping this book for years and want it as files you own, not rows in a web account
FAQ
Can I move my StoryLord continuations into Foreverse?
Through text, yes: get the original plus generated chapters out as plain text (copy or whatever export the site offers at the time), save as a txt, and import it as a book in Foreverse to keep writing. There is no one-click migrator. Recurring world facts are worth re-entering as worldbook entries so long continuations stay consistent.
Which models does each side use?
As of 2026-07 we could not find model names or a model picker anywhere on StoryLord's site — the platform decides. Foreverse is transparent by construction: 62 providers via your own keys at provider list price (keys encrypted on-device), or the official metered channel at 1 credit = $0.0001 with a 5,000-credit signup grant.
Does Foreverse have StoryLord's outline-first workflow?
No, and credit where due — the approve-an-outline-then-generate loop is a genuinely good production process for whole books. Foreverse is built around the reading moment instead: select a passage, optionally ask for a few plot directions, and grow the one you like as a branch. Book-factory workflow: theirs. Read-and-continue: ours.