About
Built by a programmer who also needed a writer’s desk.
InkVault began as a practical answer to a very personal problem: how do you shape a real manuscript without renting your own writing process?
Why InkVault exists
I am a programmer, but I am also an aspiring writer.
InkVault was not born as a pitch deck. It started from the ordinary frustration of working on a book and wanting an editing space that felt reliable, practical and truly mine.
I did not want a tool that made me depend on a monthly fee, a cloud workspace, vague platform terms or a complicated license that left me wondering what would happen to my manuscript later. I wanted to open my project, write, organize, export, back it up and keep control of the files.
That need shaped the product: local-first projects, clear structure, book-aware editing, image handling, layout checks, PDF proofing, ebook preparation, exports and backups. InkVault is software built from the inside of the writing and book formatting process, not only from the outside of a feature list.
A real manuscript behind the screenshots
CHRONICLES FROM THE FUTURE helped shape InkVault.
The text you may notice in some screenshots is not filler. It comes from CHRONICLES FROM THE FUTURE: Stories to Survive Tomorrow, my collection of short stories.
Working on that book made the missing pieces very concrete: chapter organization, revision comfort, image assets, front and back matter, export checks, backups and a workflow that did not make me feel like a guest inside my own project.
InkVault is the result of building the tool I wanted beside that manuscript.
View the book on AmazonMade for writers who want to keep their process close.
InkVault is built around ownership, local files and the practical work of turning a manuscript into a formatted print book or ebook.
See the workspace