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.
DraftAtlasA living creative knowledge system
Local-first creative intelligence for serious projects
Chart your whole project.
One compass. Seven creative paths.
DraftAtlas connects the manuscript, approved project knowledge, evidence, decisions, and creative systems behind your work across seven medium-aware paths, locally and under your control.
Local-first by design. No required account. No manuscript upload unless you explicitly choose a cloud AI provider.
Version 0.7.8
Localproject files under your control
OptionalAI and cloud providers
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 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 project outgrows folders
Serious projects stop being a stack of documents. They become connected creative systems. DraftAtlas is built for the relationships between the materials, not just the files themselves.
One connected author workflow
Write first. Let the project remember what the writing created.
The manuscript remains the work. DraftAtlas observes it, stages possible discoveries, and waits for the author to decide what becomes project knowledge.
Write in the Living Manuscript
Draft and revise without turning prose into a database form.
Review Story Details Found
Inspect evidence, confidence, conflicts, and possible canon changes.
Approve what the project should remember
Accepted details create traceable Project Bible facts, references, and backlinks.
Consult the connected project
Ask grounded questions without allowing AI to silently define the work.
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.
DraftAtlas adapts its Project Bible to the work: a Story Bible for narrative projects, a Recipe Bible for cookbooks, a Series Bible for comics, and a Lore Bible for worldbuilding and RPG projects.
A novel with chapters, scenes, arcs, motives, mysteries, and timelinesA short story with compact structure, turning points, and deliberate continuityA screenplay with scenes, sequences, locations, props, and production-aware structureA picture book with spreads, page turns, symbols, emotional beats, and illustrator notesA comic or graphic novel with pages, panels, issues, visual motifs, and series continuityA cookbook that carries family memory, recipes, testing notes, photos, and production packetsA lore bible where countries, factions, objects, histories, and myths stay connected
One product, three connected journeys
Write the work. Understand what it contains. Protect what comes next.
Every image below is a working view from DraftAtlas 0.7.8. The three primary routes show how the systems reinforce one another; the supporting views remain available for a closer look without asking every feature to compete for attention.
01
The manuscript remains the work
Write
Draft on a professional page, then decide what the project should remember. Planning and discovery stay close without turning writing into data entry.
Explore Write
02
See the whole project, not isolated notes
Understand
Trace canon, relationships, places, editorial findings, and project-grounded consultation back to their evidence in the work.
Explore Understand
03
Creative work should never feel disposable
Protect & Publish
Keep the project recoverable, inspectable, and ready to leave the app in professional formats without surrendering ownership of the source.
Explore Protect & PublishAuthor 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.
- No account required for the core app
- No telemetry in the private beta path
- No cloud sync required
- Local AI stays local when using Ollama
- Cloud AI only runs when the user configures and approves it
- Support bundles are redacted by default
Private beta
Help shape the tool built for projects that refuse to stay small.
DraftAtlas is preparing for controlled Windows testing 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
- Open the tutorial workspace
- Create a fresh test project
- Add and link one story item
- Run Story Health or Editorial Intelligence
- Export a backup
- Send a structured feedback report
Current beta status
Version 0.7.8 connects the Living Manuscript, Story Details, Project Bible, Consultation, Editorial Intelligence, visual evidence, recovery, and publishing handoff. The current focus remains proof: recovery drills, export QA, long-session performance, and feedback from real creative work.
Request AccessSupport 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.
Manuscript content is not required to ask for help.