Spines ownership of production files

This clause turns production help into a lock in mechanism. Spines lets authors keep the copyright, but it keeps ownership of the working ebook, audiobook, and print files it creates, which means leaving Spines can require either rebuilding those files elsewhere or paying a large release price. In practice, that makes Spines look less like a simple service provider and more like a managed publishing stack that keeps control of the finished production assets.1 2 3 4 5

• The key split is copyright versus production files. Authors still own the underlying manuscript and rights, but the formatted EPUB, print interior, cover package, and produced audiobook are separate assets in day to day publishing, because those are the files retailers and printers actually need.1 5
• This is a meaningful contrast with Amazon KDP and IngramSpark. Those tools are lighter weight and require more author labor, but they are built around the author supplying or controlling the publishable files. Spines does more of the hands on production work, then keeps tighter control over the outputs it created.2 3 4
• The economics match that structure. Spines charges package fees, takes a share of net sales, and can also retain a non exclusive license to use the book, including for model training. That gives it value from both the service transaction and the content and file layer around the book.1 5

The likely direction is a sharper split across self publishing. Low cost tools will keep attracting authors who want full control of files and vendors, while managed AI publishers like Spines will push toward owning more of the production workflow in exchange for speed, coordination, and convenience. That makes file control a central competitive lever, not a legal footnote.2 3 4 5