DraftAtlasThe living knowledge system behind the book

Local-first creative intelligence for serious projects

Every story becomes too big to remember.

Characters multiply. Relationships evolve. Timelines branch. A sentence you wrote three months ago becomes the hinge of the ending. DraftAtlas is the place where an entire creative world stays connected, so the author can keep writing without losing the thread.

Local-first by design. No required account. No manuscript upload unless you explicitly choose a cloud AI provider.

Project AtlasBeta 0.5
Actual DraftAtlas Character Web showing connected story entries, weighted relationship lines, and selected-entry context.
100%author-owned project files
0required cloud services
7medium-aware project types

Why it exists

The problem is not writing. The problem is remembering what the writing created.

DraftAtlas is not competing with the blank page. It is competing with scattered notes, half-remembered decisions, disconnected folders, and the quiet fear that an important thread has slipped out of sight. It gives the world behind the manuscript a structure the author can trust.

The writer's burden

DraftAtlas gets more valuable as the project gets larger.

A simple document can hold text. A serious creative project needs memory: who knows what, where something first appeared, why a symbol matters, and what still needs to be resolved.

The side character returns

You introduced them months ago. Now they matter. DraftAtlas helps you find where they first appeared, who knows them, what they touched, and which threads now depend on them.

The small detail becomes central

A cup, a key, a family recipe, a symbol, a line of dialogue. DraftAtlas keeps the object, meaning, scene history, and backlinks together instead of leaving them scattered across notes.

The timeline starts to argue

Characters travel, ages shift, revelations happen too early, and chapters move. DraftAtlas gives continuity a place to surface before readers notice the crack.

The book outgrows folders

Serious projects stop being a stack of documents. They become worlds. DraftAtlas is built for the connections between the pages, not just the pages themselves.

Medium-aware memory

Your project should not have to pretend to be a novel.

A picture book remembers page turns and recurring images. A cookbook remembers recipes, testing, family history, and production notes. A lore bible remembers worlds, factions, artifacts, and history. DraftAtlas changes the map to fit the work instead of forcing every creator into the same outline.

A novel with chapters, scenes, arcs, motives, mysteries, and timelinesA picture book with spreads, page turns, symbols, emotional beats, and illustrator notesA cookbook that carries family memory, recipes, testing notes, photos, and production packetsA lore bible where countries, factions, objects, histories, and myths stay connectedA comic or screenplay where pages, panels, scenes, props, and dialogue need structureA manuscript that can be drafted without leaving the knowledge system behind

What you are looking at

Screenshots should prove the app remembers what the author cannot hold alone.

These are actual DraftAtlas beta screens. Each one shows a different kind of project memory: where work lives, how entries link, why relationships matter, what needs review, and how the author stays in control.

Author ownership

Your manuscript should not need a server to exist.

The project belongs to the person making it. DraftAtlas is built around local project folders, backups, redacted diagnostics, and user-controlled exports. Cloud services are optional. AI is optional. Privacy is the default, not a premium feature.

Private beta

Help shape the tool built for projects that refuse to stay small.

DraftAtlas is entering a controlled beta focused on trust: data safety, backup and restore, first-run clarity, export honesty, local AI behavior, and real creative workflows from writers who will actually use it.

Start Beta Test path

  1. Open the tutorial workspace
  2. Create a fresh test project
  3. Add and link one story item
  4. Run Story Health or Editorial Intelligence
  5. Export a backup
  6. Send a structured feedback report

Current beta status

The app is feature-rich and usable, but still being hardened before broad release. Known beta focus areas include installer polish, destructive backup testing, export QA, tutorial clarity, and long-session performance.

Help shape DraftAtlas

Support and feedback

Trust also means knowing what you are sending.

DraftAtlas feedback is structured around categories, severity, reproduction steps, diagnostics, and privacy preview. Support bundles are redacted by default so testers can report problems without accidentally sharing manuscript text, notes, prompts, images, or private project names.

Contact

For beta interest, issue reports, or questions, email support@draftatlas.app.

Support mail is handled through Google Workspace for the DraftAtlas domain.