Inside Folian

A closer look at the writing OS for long-form fiction.

Folian is built around a simple belief: a novel needs more than a place to type.

The harder parts of writing are not always visible on the page in front of you. They live in the character history, the world rules, the chapter plan, the style decisions, the canon and the quiet promises the book has already made to the reader.

That is why Folian is being designed as a writing OS, not just another editor with AI attached.

It gives the manuscript, story bible, characters, lore, canon, planning and AI support a shared home, so the writer can work with the whole book rather than constantly trying to hold the whole book in their head.

Start with the whole project

A long-form writing project is more than a document.

It is a manuscript, a plan, a story bible, a set of characters, a world, a style, a timeline, a revision process and a memory of decisions already made.

Folian gives those parts of the project a shared home.

The goal is not to make the writing process heavier. The goal is to stop the important parts of the book from being scattered across documents, notes, chats and half-remembered decisions.

When those layers are connected, the writer has a clearer view of the work and AI can be used with far better context.

Project dashboard

The project dashboard gives writers a clear place to return to.

From here, a writer should be able to see the shape of the book, move into the manuscript, check the story bible, review planning notes and understand what needs attention next.

This matters because novels can become sprawling quickly. A writer may be dealing with chapters, characters, locations, world rules, unresolved questions, drafts and revision notes all at the same time.

The dashboard exists to give the project a centre, so the writer is not constantly digging through separate documents to find the next important thing.

Manuscript workspace

The manuscript is where the story becomes real.

Folian is designed to keep the manuscript close to the rest of the project, so drafting does not become separated from the information that gives the book its shape.

A scene is not only a scene. It belongs to a chapter, an arc, a character history and a wider story logic. When those layers are connected, the writer has more control over what the scene is meant to do.

This is especially important when AI is involved, because AI can easily produce a scene that reads well but does not belong in the book. Folian is being built to make that less likely by keeping the manuscript connected to the surrounding story context.

Story bible

The story bible is where the book keeps its truth.

Characters, locations, lore, world rules, timelines, open questions, reveals and important facts all need somewhere to live.

For writers using AI, the story bible becomes even more important because it gives the system a way to understand the project beyond the immediate prompt.

Without a connected story bible, the writer has to keep reminding the AI what the book already knows. That turns AI into something that needs constant supervision rather than something that can genuinely support the writing process.

Characters

A character is not just a name, age and description.

A useful character record should hold motive, wound, fear, desire, contradiction, relationships, secrets, voice and change.

Those details matter because long-form fiction depends on continuity of behaviour. A character can grow, but they should not accidentally become a different person because the system lost track of who they were.

Folian is being built to help writers keep character truth close to the manuscript, where it can actually support the writing.

Lore and locations

Worldbuilding becomes difficult when the notes are scattered.

A location introduced in chapter two may become important in chapter twenty. A rule created for one scene may shape the ending. A piece of history may explain a character's fear, a political conflict or the reason a place feels dangerous.

Folian gives writers a structured way to manage the world around the story.

For fantasy writers, series authors and worldbuilders, this is not decoration. It is the architecture of the book. If the world is inconsistent, the reader feels it, even if they cannot immediately explain why.

Canon and continuity

Canon is what the story has made true.

Once something is true in the manuscript, the rest of the book has to respect it unless the writer deliberately changes it.

That is easy enough in the early pages. It becomes harder as the story grows, especially when AI is involved and can confidently suggest details that sound right but do not belong.

Folian is designed to help writers protect the thread of the story.

Less drift.

Fewer accidental contradictions.

More control over what the book knows.

Planning workspace

Before a chapter works on the page, it often has to work in structure.

The planning workspace is for arcs, chapters, scenes, notes and the decisions that shape the manuscript before or during the draft.

Some writers plan heavily before they begin. Others discover the story as they write. Folian should support both, because planning is not about forcing every writer into a rigid outline.

It is about giving the story enough structure to survive the long middle, where many manuscripts begin to lose direction.

Style profiles

Style is not decoration.

It is rhythm, restraint, sentence movement, point of view, texture, dialogue and taste.

One of the biggest risks of AI-assisted writing is that the prose becomes smoother but less specific. The language becomes easier, but the voice becomes less yours.

Folian's style profiles are designed to help writers capture the qualities they want the AI to respect, so assistance does not turn into flattening.

The writer still decides what stays.

The system helps preserve the direction.

AI provider settings

Folian is designed to support a bring-your-own-keys model.

That means writers can connect supported AI providers such as OpenAI or Claude where available, choose the provider they want to use and keep more control over their setup.

Folian provides the writing system.

The AI provider supplies the model.

The writer decides how and when AI belongs in the process.

This is important because different writers will use AI in different ways. Some may use it lightly for brainstorming, others may use it for style review, chapter planning or revision support. Folian is being designed to give the writer choice rather than forcing one fixed workflow.

Learn about bring-your-own AI keys

Export and project control

A serious writing project needs to leave the system cleanly.

Folian is being built with export in mind, including manuscript exports, project backups, canon bundles and writing materials that can support revision, beta reading, submission or future work.

The writing system should help the author finish the book, not trap the book inside the system.

That principle matters because writers need ownership of their work. Folian should support the book, not become the only place the book can exist.

Read the full product overview