Roadmap and early access

What InkVault does now, what is evolving, and what is not promised yet.

InkVault is being built as local-first publishing software for writers who need planning, manuscript cleanup, layout control, PDF proofing, EPUB-oriented export and private project ownership.

Product status

Roadmap clarity matters more than feature noise.

The goal is to be honest about what belongs to the core workflow, what is being refined, and what would require a separate product decision.

Core

Local book production

Chapters, notes, metadata, layout settings, images, cleanup, preflight and exports in one project.

Now

Private ownership

Work around local files, local backups and author-controlled project folders instead of a mandatory cloud account.

Next

Sharper output checks

More practical warnings for margins, covers, images, EPUB validation and PDF tool readiness.

Roadmap areas

Planned and evolving product areas.

Print PDF proofing

Refine page geometry, portrait/landscape layouts, margin checks, PDF proof generation and export environment validation.

EPUB workflow

Improve metadata, navigation, image handling, validation checks and ebook-oriented export reliability.

Preflight

Expand warnings for trim size, gutter, covers, images, empty chapters, broken structure and missing export tools.

Image-heavy books

Strengthen full-page, full-bleed, optimized variant and resolution checks for illustrated and nonfiction projects.

Backups and snapshots

Improve local backup clarity, milestone preservation and recovery expectations without turning InkVault into mandatory cloud storage.

Self-hosted path

Clarify compatible server requirements, deployment checks and private infrastructure responsibilities.

Current non-goals

Some features are intentionally not presented as done.

This matters because the comparison page is strict. A feature should not be treated as available until it has a real, testable workflow.

Not current core features

  • KPF export: would require a dedicated Kindle Create/Amazon package path.
  • Managed cloud storage: conflicts with the default local-first positioning unless offered as a separate option.
  • Real-time collaboration: would require permissions, conflict handling, history and review workflows.
  • Track changes: would need a document revision model, not just plain content edits.

Early access expectations

  • Feature details may change before full public release.
  • Every publishing export still needs proofing by the author.
  • KDP and distributors remain final validators.
  • Self-hosted deployment depends on server configuration and maintenance.

What will not change

The center of the product is still the author-controlled book project.

InkVault should keep solving the messy production stage: scattered structure, disconnected notes, imported formatting noise, uncertain margins, image problems and export checks.

FAQ

Early access questions

Is InkVault finished software?

InkVault is presented as early access. The core direction is clear, but some production workflows, export details and deployment paths may still change before a full public release.

What does early access mean here?

Early access means buyers should expect a product that is usable in its intended direction but still evolving. It is best for people who accept careful proofing, feedback loops and possible workflow changes.

Does the roadmap promise KPF export, cloud storage or real-time collaboration?

No. Those areas are listed separately because they are not current core features. KPF export would require a dedicated Amazon-format path, while cloud storage and real-time collaboration would change the local-first product model.

Are PDF and EPUB exports final?

Export workflows must always be proofed. InkVault can help with structure, layout, validation and preflight checks, but KDP and other publishing platforms remain the final validators.

Will local ownership remain part of the product?

Yes. Local-first project ownership is a central direction for InkVault, even where self-hosted or hybrid deployment options are explored.

Next steps

Related workflows

Compare tools

See how InkVault compares with Atticus, Kindle Create, Reedsy Studio, Scrivener and Vellum.

Open comparison

Problems solved

Review the author and production problems InkVault is built to remove.

See problems

Feature overview

Review the practical workflow from planning to export.

Open overview