About Bookloft
A publishing house built this, not a software company.
Bookloft started as Durii Editorial's internal tools. The analysis engine was written because there was a pile of unread submissions and no free afternoons. The royalty statements, because reconciling them by hand took days of work every year. The catalogue record, because metadata was being typed twice.
None of those modules was designed on a whiteboard: they were written the day they were needed, used the next day and fixed within the month. That has a practical consequence you can feel while using it — when something in the craft doesn't fit the software, here it's the software that changes.
In 2026 it was separated from the publishing house so it could be sold to others. And with that separation came the rule that governs everything built since: nothing about how Durii works is wired into the platform. Royalty tiers, periods, channels, VAT, advances, the red lines of selection — all of it is each house's configuration, not a house default.
Durii is Bookloft's first customer. Not its owner, and certainly not its rule.
What isn't up for negotiation
01What isn't up for negotiation
- 01Editorial judgement is human. Bookloft proposes and leaves a record; an editor signs.
- 02A manuscript belongs to whoever wrote it. We don't train models on them.
- 03No way of working is imposed. What one house does isn't the rule for the rest.
- 04No figure without measuring it. If it can't be measured, it isn't published.
- 05A submission that arrives gets read in full. There is no sampling.
Talk to us
02Talk to us
If you run a publishing house and want to know whether this fits, write to us and we'll take our time over it. People answer.
Fourteen days to test it with your own books.
Upload a manuscript and let it read. Import twenty books. Produce a royalty statement. That will tell you.
14 days · nothing is charged today · cancel whenever you like