Local ownership and security

Own the manuscript workflow, not just the final export.

InkVault is designed around local project files, controlled backup locations and optional private server deployment for writers who do not want a mandatory manuscript cloud.

Local-first principle

Your project should remain understandable outside the app.

The ownership goal is simple: manuscript content, images, metadata, exports and backups should live in a workspace the user controls. That makes the workflow easier to reason about and easier to back up.

  • Local folders for project files, images and exports.
  • No mandatory cloud account for normal manuscript work.
  • Backups and milestone concepts close to the book project.
  • Self-hosted option for private server workflows where appropriate.

Security responsibilities

  • Use reliable backups on more than one storage location.
  • Use disk encryption for sensitive manuscripts.
  • Protect access to the computer or server running the software.
  • Keep server software updated if using self-hosted deployment.

What local ownership helps with

Practical control for long-term manuscript work.

File clarity

Projects, images, exports and backups are easier to locate when they live in controlled folders.

Backup policy

Authors can choose backup destinations and preserve manuscript states before major revisions.

Offline work

Normal writing, layout and export preparation should not depend on a remote writing account.

Private server

Self-hosted deployment can support private browser access on compatible customer-controlled infrastructure.

FAQ

Local manuscript ownership questions

Does InkVault store my manuscript in the cloud?

InkVault is designed around local-first project ownership. Normal manuscript work is intended to happen in files and folders controlled by the user, not in a mandatory cloud workspace.

Are local files automatically safe?

No. Local ownership also means backup responsibility. Users should keep redundant backups and use operating system or disk encryption when confidentiality matters.

What about the self-hosted edition?

The self-hosted path is intended for compatible private Linux servers owned or controlled by the customer. Server security, permissions, updates and backups remain important operational responsibilities.

Next steps

Related workflows

Offline publishing software

Explore the workflow built around local project files.

Offline workflow

Roadmap

Understand early access status and planned product areas.

Read roadmap

Privacy

Review website and account data handling information.

Privacy policy