I was surprised at how many template settings that seem basic to me are hidden and can be changed only by Paligo support.
On further reflection, though, this matches the way people use DocBook and DITA in large companies: they have developers who handle that stuff. I hope Paligo has built that into their pricing. At first $3,108 per writer per year might seem expensive, but when you consider total cost of ownership including hosting, IT, and custom development, it's potentially a very good value for small teams.
For comparison, I'm a sole writer with >30 reviewers, so maintenance and support for Confluence, Scroll PDF Exporter, and Scroll HTML Exporter at the 50-user tier is currently $1750 a year, plus around $1200 for Amazon EC2 hosting. Since we need versioning and workflow management, if we stick with Confluence I'd have to add Comala Workflows and Scroll Versions, which would cost $2000 for the first year and $1000 after that. Thus Paligo is cheaper than sticking with Confluence, plus we have a single point of support.