Livingdocs combines a modern editing experience with a robust, API-driven platform, delivered as a managed cloud service. Built for professional publishing, it integrates seamlessly into existing systems while supporting the scale and complexity of large newsrooms.
The following sections outline how Livingdocs is built and operated—from our managed cloud infrastructure and underlying technologies to security practices and scalability characteristics. Together, they provide a transparent view into how the platform performs in demanding, real-world publishing environments.
Livingdocs runs on Kubernetes in Microsoft Azure, operated end-to-end by our team. Your engineers stay focused on the website and apps your readers see and never have to run a CMS. Your editorial team never has to wonder whether the platform is up. And you don't get a blank platform: we bring the publishing know-how we've built running Livingdocs for some of the largest German-speaking newsrooms, applied to your setup. Workflows, document types, roles, and integrations are all configured alongside your team. Product releases ship on a steady bimonthly cycle, and improvements roll into your environment continuously between them, each change rehearsed first in a dedicated staging environment so nothing lands in the middle of a story. When something does need attention, one accountable team is on call around the clock under a 24×7 SLA.
Livingdocs is headless and API-first by design. Editors work in a single workspace, and the same structured content flows out to every channel you serve: web, app, newsletter, and print, without re-authoring. That's the point of headless for a newsroom: one source of truth, many surfaces, no parallel CMSes for the apps team and the web team to keep in sync. A documented REST API and event webhooks make it straightforward to plug Livingdocs into the rest of your stack, including your DAM, archive, analytics, CDN, and AI assistants. The API uses release-date-based versioning with a two-year minimum support window per version and at least six months of advance notice before anything is deprecated, so the integrations your team builds keep working as the platform evolves. The platform itself runs on Node.js with PostgreSQL, Elasticsearch, and Redis on Kubernetes, instrumented end-to-end with OpenTelemetry, Prometheus, and Grafana, which we use to tackle issues proactively.
Livingdocs is designed with a strong focus on secure and controlled content operations. Sign-in goes through your identity provider, with fine-grained permissions through project-based user groups and scoped API tokens that support rotation and expiration. Each customer runs in their own isolated environment, with separate data, separate infrastructure, and no shared tenancy. Every action, whether by a journalist, an integration, or an AI assistant, is attributed and auditable, which matters when editorial accountability is on the line. We host on Microsoft Azure in Germany to meet European data residency and GDPR requirements, and all data is protected in transit. We commission independent penetration tests and continuously monitor dependencies so we can react quickly to emerging vulnerabilities.
Livingdocs runs in production at major European publishers — newsrooms with editorial teams of 500+ and content libraries of millions of articles, images, and assets. The platform is built for horizontal scalability, with separate services for the editor, APIs, and background processing, so we can grow exactly the part that is under load. Before anything unusual, such as a large content import, a redesign, or an election night, we plan capacity with you in advance.
Our bimonthly release notes break down what's new, what's changed, and what's coming. Subscribe to stay in the loop.
