If you have written a long fan story, you probably know how a small continuity error can break momentum. Three months into a side story set in a universe I had loved for years, I gave one supporting character two different surnames four chapters apart. Not a twist, just an error I noticed on a slow reread, with the thought that earlier chapters might hold others.
I spent an afternoon checking for inconsistencies and found six more. Then I stopped writing for three weeks.
That kind of failure is common in fan fiction. You are working within a universe built by someone else, alongside characters your readers may know better than you do, while trying to tell a new story. Holding all those facts together creates cognitive overhead that writing tools have never really been designed to ease.
Tools not made for this
In original fiction, you create every fact about the world and keep track of it yourself. In fan fiction, you work within an established universe, a timeline controlled by someone else, and characters whose voices readers expect you to respect.
The tools fan writers use generally treat both kinds of writing alike. A word processor does not know that a mentor died before your story starts, or that two scenes in your timeline occur far apart. Wiki pages offer useful reference, but remain in another tab. Checking consistency stays manual and disruptive.
The usual solution is a character sheet beside the draft. Experienced fan writers create detailed spreadsheets with relationship maps, timeline tables, location lists, and records of established facts. They help, but share one basic weakness: reference and writing remain separate. Each check means leaving the draft, searching for an answer, and holding it in mind while you return to the page.
For a short one-shot, that interruption is manageable. Across a long story posted chapter by chapter for months, it builds up. It is a major reason fan fiction projects enter indefinite hiatus.
What we wanted to build
Arjun and I began building Fanon in 2023. Arjun had experience with NLP systems and language model infrastructure, and believed the technical pieces were ready for our idea: context-aware retrieval, character voice modeling, and lightweight lore validation. The harder question was whether to shape the product around fan writing, which differs from general creative writing in important ways, instead of treating fan fiction as another use case for a generic writing assistant.
Our early conversations kept circling the difference between a writing assistant and a writing partner. An assistant completes your text. A partner who had read your work would notice a contradiction, recognize how a character speaks from studied examples, and understand that you are writing within an established world rather than inventing without constraints.
That was the thing we wanted to make.
Priya and the community side
Priya joined six months in, with a background in fandom community management. She brought Arjun and me something we lacked: a close view of how fan writers work day to day, including the social layer that general writing tools largely overlook.
Fan writing is not always solitary in the way original fiction can be. Writers post chapters, readers respond between installments, and those reactions can affect what comes next. Headcanons also grow together in comment threads and discord servers. Our tool had to belong within that ecosystem, not replace or avoid it.
Much of what separates Fanon from a generic writing assistant reflects Priya's influence: community publishing, the relationship between drafts and reader feedback, and AI as a consistency layer rather than an authorial voice. These were design choices, shaped by observing how fan writers actually spend their time, not merely technical choices.
What Fanon is not
We want to make two points clearly. Fanon has no official relationships or partnerships with intellectual property owners, franchises, or studios. It is an independent tool for fan creators. The universe lore you build and maintain in Fanon is your own, grounded in your reading and interpretation of source material. That is the setting in which fan creation has always operated. Fanon is not a licensed product, and we do not claim that it is.
By not replacing the writer, we mean Fanon generates options for you, not that it writes the story in your place. The tool proposes. You decide what belongs, what does not, and what captures your intent. Creative judgment stays with the person writing.
We want to remove friction that does not call for creative judgment: the fifteen-minute search to confirm a timeline detail, the contradiction missed after two months away from a project, or the challenge of finding a character's voice again when beginning a new chapter.
What we saw so far
We opened early access to writers in the first half of 2026. The patterns were useful and not quite what we expected. We thought plot continuation would dominate, with writers asking the system for the next scene. Instead, they used it to explore character voices before writing difficult scenes, test new backstory details against an established timeline, and create alternate versions of scenes they wanted to revisit.
It was used less as a ghostwriter and more as a partner for the most friction-filled parts of writing.
We are three people in Koramangala, building something we needed as writers ourselves. The questions from early access are the ones this journal will keep exploring: craft in fan writing, the relationship between writing and reading communities, and the places where a tool like this helps or gets in the way.
If you have written fan fiction for a while, you likely know which obstacle you would remove first. Tell us about it. We would be glad to hear what you are working through and invite you into the conversation.