Lorien

Multichannel publishing platform

Create once. Publish everywhere.

Lorien is a content platform built for news media. One newsroom creates content once, and it publishes to websites, mobile apps, print, newsletters, and any other channel through one content model and one set of APIs.

01 / Content planning

Plan, assign, and publish in one place

Planning lives inside the CMS, not in a separate tool bolted on the side. A story is planned, assigned, drafted, and published in one system, so there is no sync gap between the plan and the content.

Feature Description
Editorial lifecycle Content moves through Plan, Task, Draft, Publish, and Optimize stages. Plans carry a title, description, size estimate (S/M/L/XL), deadline, linked assets, contributors, teams, and keywords.
Four planning views A sortable Plan list with nested tasks; a Plan timeline board with a configurable 1 to 7 day range and separate print and digital sub-views; a paginated Task list with assignee, team, status, and deadline columns; and a Task calendar with week and day views.
Plan across titles A single plan can target one title or several at once, so the same story is planned once and scheduled separately per title and channel rather than re-entered for each brand.
Everything about a story in one place A plan gathers its linked assets, tasks, background attachments, contributors, keywords, and per-channel schedules in one view, so nothing about a story is scattered across tools or inboxes.
Assignments and work orders A plan breaks into tasks assigned to people or teams, each with a status and a deadline. Editors filter the Task list and calendar by assignee and team to see who is working on what.
Per-channel publish planning A single plan can schedule publication separately for each channel and place content into named slots. In print, slots are departments such as Sports or Opinion; online, they can be publishing windows such as Morning, Post-lunch peak, Afternoon, and Before bedtime, so subscribers get a steady flow of fresh content through the day.
Named filter presets One-click filters like "My tasks", "My unfinished tasks", and "Ideas". Editors can also save and name their own filters.
Drag-and-drop scheduling Schedule and reschedule content by dragging cards in the timeline and calendar views.
Collect material from freelancers A public submission link lets occasional contributors send in material that lands straight on the related work order, with no account or manual file handling in between.
02 / Editorial experience

One workspace, idea to publish

The newsroom works in one fast editorial interface. From the first idea to the published story, writing, editing, media, metadata, and publishing all happen in the same place, with no separate tools to switch between.

Feature Description
Modern editorial workspace A web-based editorial interface built for fast newsroom work, with inline editing, drag-and-drop, and quick-create actions. There is no desktop software to install or maintain.
Works on any device The interface is responsive, so browsing, searching, editing, and publishing work on desktop, tablet, and mobile. The experience is richest on desktop, and mobile handles quick updates, checks, and publishing well.
Rich article composition Articles are built from more than 40 content block types, including inline images, video, audio, graphics, fact boxes, expandable sections, pull quotes, tables, galleries, social embeds, and reader-submission forms.
External embeds Questionnaires, interactive data visualisations, and third-party widgets embed directly into articles through HTML embeds.
Finnish spell-check and style help Voikko Finnish spell-check is built into the article editor with real-time inline highlighting, and AI adds grammar and style suggestions as part of content quality checks.
Preview before publish Content can be previewed before it goes live through a secure token-based preview on the Delivery API, rendered by the actual front end, with print preview through the print pipeline.
Fast, structured metadata Each asset type has its own metadata form with sensible defaults and validation, and AI can suggest SEO titles, summaries, and headlines for an editor to approve.
Keyboard-driven editing The article editor supports standard keyboard shortcuts for text formatting, block operations, and navigation.
Roles and permissions Access is controlled by per-user and per-team roles with fine-grained permissions, down to per-asset access control lists. Occasional contributors can be scoped to submit through a public link, while regular contributors get editor access with task assignments.
Single sign-on and federation Upcoming Identity runs on AWS Cognito with SAML 2.0 and OIDC federation, so accounts connect to the identity providers a publisher already uses.
03 / Multichannel publishing

One asset, every channel, its own rules

The publishing model is built around one idea: content is created once and published to many places, each with its own rules.

Feature Description
Create once, publish everywhere A single asset publishes to any combination of websites, print editions, mobile apps, and newsletters. There is no copying between systems or brands.
Publish decisions per channel Each channel a story appears on gets its own publish decision, carrying its own publication time, visibility, priority, access policy, and embargo. The same story can go live at different times on different brands.
Full traceability Every publish decision is tracked with full history, so it is easy to see not just what is live now but what was live before.
Isomorphic content Article content is stored as structured blocks, not as channel-specific HTML, so the same content renders correctly on web, mobile, and print. Block visibility can be tuned per channel, for example showing descriptive text in place of a video in print.
Print and digital in one version Specialized fields such as print title and print lead live alongside the digital ones in a single version, so print and web stay in step without duplicate records.
Brand variants When a story needs a local angle, a new version on the same asset carries its own publish decisions, keeping the variants linked.
Newsletters and social from the same content Newsletters and social channels publish from the same content through the APIs and per-list RSS feeds, so they are not separate production steps.
Managed Lists Front pages and section pages are built from Managed Lists, which combine manual editorial picks with automatic generators such as newest content, most popular, trending, editorial recommendations, marketing content, games, and HTML embeds. A Managed List automatically avoids showing the same story more than once.
Nested lists A front-page list can include sub-lists maintained by other desks, such as sports, culture, or local, so each desk curates its own section while the front page brings them together.
Every list is an API and an RSS feed Each Managed List has its own API resource and RSS feed, so any list can be consumed headlessly by an app or a third party.
04 / Print automation

Print is a channel, not a second workflow

Print is a delivery channel, not a separate workflow. The same content that goes to the web flows to the printed paper through an automated pipeline, built on the Aptoma DrEdition platform.

Feature Description
Online content flows to print Content planned and published online becomes available for print automatically, so a story reaches the printed paper without being re-entered or copied. Publish decisions on digital channels can be mirrored to the associated print channels.
Browser-based layout, no InDesign Pages are laid out in the browser. The workflow from article placement to print-ready PDF happens without desktop publishing software.
Automatic article placement The Placement Bot distributes articles across page space and generates layouts automatically. About half of a typical page comes out ready, and editors refine the rest.
Automatic layout fitting The layout engine generates layout variations for given page dimensions and fits typography, image scaling, and text flow to the available space automatically.
Automated ad placement Ad positions are placed on the page from placement codes and coordinate with the article layout, so editorial and advertising space work together. Editors can adjust placement manually.
Editors stay in control Automation produces a starting point, not a locked result. Editors can override any automated placement or sizing decision on any page.
Finnish hyphenation Finnish hyphenation is built into the layout engine and is configurable per element, such as headlines, body text, and captions.
Multi-target delivery When an edition is archived, finished pages are delivered in parallel to multiple targets such as the print house, e-paper, the national library, press distribution, media monitoring, and archives, with independent retry per target.
Ads and PDF content to print Booked ads flow to print, including placeholders for ads that are sold but not yet finished, and PDF content such as comics, weather graphics, and TV guides publishes to print channels.
Editions and supplements at scale The pipeline scales to dozens of titles with their editions and supplements, with reusable styles per title and pages that can be shared between papers.
Print feedback loop When pages are sent to print and the edition is archived, the platform records exactly which page and which paper each article appeared on. That creates a full audit trail back in the content system.
Regional editions A parent edition can feed regional child editions that inherit its pages, with individual pages disconnected for local editing where needed.
Less desktop-publishing licensing Because layout happens in the browser, demand for desktop publishing licences drops. Highly custom layouts can still be prepared externally and added as a print-ready PDF.
05 / Media & assets

Every content type, one model

Everything is an asset, versioned and searchable through the same interface, whether it is text, an image, or a video.

Feature Description
One system, no separate DAM Media management is part of the editorial interface, not a separate digital asset manager. Every newsroom works from one shared content pool through the same search, browse, and filter tools.
Article The core editorial content type, composed from rich content blocks. Articles come in genres such as news, features, profiles, and opinion pieces, so publishers can give each genre its own look and feel online and in print.
Image Photos are managed as first-class assets with rich metadata, and every image stays searchable and reusable from one shared pool, with no separate archive to move content in and out of. Because each photo is a single asset, the platform knows where it has been used, so editors can avoid repeating the same image across stories.
Video Long-form and short-form video, with native Flowplayer and Vimeo support, and videos hosted on external services can be published as native assets too.
Audio Audio content managed alongside every other asset type.
Gallery Curated collections of images and videos that can be published as their own content, a good way to make full use of a photo shoot rather than only the few frames that make it into an article.
Web Story Full-screen, tappable stories built for mobile.
PDF PDF documents delivered to print and digital channels.
Graphic Visual graphics and infographics.
Cartoon Comic strips for print and digital, including syndicated strips.
Game Puzzles and games.
Podcast episode Episodes that make up a podcast series.
Version history Each asset has one or more versions with immutable version numbers, status tracking, and a full audit trail of who created and changed what, and when. Different versions can be live on different channels at the same time.
Image delivery CDN Images are resized and reformatted on request, so there are no pre-generated thumbnails to manage. Smart cropping keeps the subject centred across aspect ratios.
Automatic image metadata IPTC and EXIF metadata is detected from uploaded images and prefilled, so photographers and editors spend less time on data entry.
Rich image metadata Photographer, caption, capture date, dimensions, and EXIF and IPTC metadata are tracked per image.
Reader-submitted photos and videos Readers send in photos, videos, and news tips through a web submission form or by SMS and MMS. Submissions arrive automatically in the newsroom content pool, tagged as user-generated content with their own rights and access metadata, where an editor picks what to use. No manual file handling in between.
Reuse across brands Any image or media asset in the shared pool can be reused across brands and channels without duplication.
Source tracking Every asset can record where it came from: source system, source organization, external ID, and arbitrary metadata. That makes migration, syndication, and re-import traceable.
06 / AI & automation

AI on open standards, human in the loop

Lorien AI is a multi-agent system built on open standards, with a human in the loop wherever AI touches published content.

Feature Description
AI in the newsroom, not a separate tool AI is available to content creators directly inside Lorien, so there is no separate jungle of tools to move between.
Model Context Protocol servers AI tools are integrated with Lorien AI using the Model Context Protocol (MCP), a standard interface for connecting tools to AI agents.
Dynamic Skills AI capabilities are packaged as Skills that can be built and deployed independently, so new capabilities can be added without code changes.
Metadata recommendations In the article editor, AI suggests SEO titles, meta descriptions, summaries, and headlines for both print and digital. Suggestions need editor approval before they save.
Comment moderation (Klaara) One production example of the AI stack at work: Klaara moderates reader comments at more than 99% automation. The moderation workflow itself is covered under Audience and access.
LLM observability Every AI call is tracked for cost and performance, so AI use stays measurable and accountable.
Customer-built AI Customers can build their own AI workflows using the MCP protocol, the Skills framework, the Management API, and platform events.
Automatic audio versions Upcoming AI turns a published article into a natural-sounding spoken version, created as an alternative rendition of the same asset, so readers can listen to a story on web and mobile. Every AI-generated audio asset is fully traceable, down to the model, prompt, and tool use behind it.
07 / Audience & access

Readers, access, comments, and revenue

The platform handles reader accounts, access, comments, and personalization, and the commercial models around them, and connects to the consent systems a publisher already runs.

Feature Description
Commenting Hodor, the commenting service, supports threaded discussion and per-thread account requirements.
Automatic moderation Klaara, an LLM-based service, moderates comments at more than 99% automation, which removes most of the routine moderation load before a human sees anything.
Moderation tool Comments that need a human decision come to a moderation interface where editors approve, reject, or edit them. The automatic and manual paths work together: Klaara clears the clear cases, people handle the rest.
Mobile personalization My Lorien lets readers follow the keywords they choose and bookmark content for later, powering personalized feeds in mobile apps.
Access policies Access can be free, login required, source-based, or premium and subscriber-only. Each asset carries a default policy, each site applies its own default to new content, and either can be overridden per publish decision. So the same story can sit behind a strict paywall on one site, run free on another, and open up over time.
Native advertising Native ads are created and published as first-class assets, with a clear separation between journalistic, commercial, and user-generated content.
Ad serving and reporting Built-in sites support dynamic ad loading to make the most of inventory, and closed-loop ad reporting through CRM integration tracks which ads ran where.
Consent management Gravito integration handles GDPR cookie and tracking consent on public sites.
09 / APIs & integrations

Built to be built on, and to connect

Lorien is built to be built on and to connect. Your developers get first-class APIs, complete documentation, and AI-assisted tooling, and the same API-first, event-driven design connects Lorien to the systems you already run.

Feature Description
Two REST APIs A Management API covers full content creation, editing, publishing, and administration, and a read-only Delivery API serves published content to websites, apps, and external consumers. Both are REST and return structured JSON, with full operations on every asset type.
Full developer documentation Complete, versioned documentation covers both the Delivery API and the Management API, so your developers are productive from day one.
Claude Code plugin A single plugin turns Claude Code into your team's Lorien API expert across the Delivery and Management APIs, with tools that always pull the latest documentation, so developers build API clients and integrations in minutes.
Built for AI-assisted development The API-first design and documentation are made for AI as well as people, so coding agents understand Lorien's interfaces and build new tools and integrations efficiently.
Event-driven architecture Significant changes in the platform are published as events that external systems can subscribe to, so integrations and tools react in real time instead of polling for changes.
Newswire and photo ingest Ready integrations to newswire and photo services such as STT and Lehtikuva bring wire copy and images into the newsroom automatically, available to journalists and editors the moment they arrive.
Advertising and CRM Ready integrations for ad trafficking and ad serving (Adpoint, Equativ) and for CRM and ad reporting (Salesforce).
Weather Live weather data through Foreca.
Games and puzzles Games and puzzles through Keesing.
Syndicated cartoons Comic strips from syndication providers such as Bulls, PIB, and Testikuva, with automated publishing to print and digital.
Headless consumption Every Managed List exposes an API resource and an RSS feed, so content flows to any front end or partner without a bespoke export.
10 / Platform & security

Cloud-native, multi-tenant, EU-resident

Lorien is cloud-native and multi-tenant, with EU data residency and the operational practices a production newsroom depends on.

Feature Description
Cloud-native architecture Microservices run on Kubernetes on AWS, defined as infrastructure as code and deployed through an automated pipeline.
Multi-tenancy Multiple brands can run on one installation and one database and pool content freely, while newsroom-filtered views and saved searches let each team focus on its own brand.
You own your data Your content and data are yours, kept in a dedicated database that stays private to you.
EU data residency All content and user data is stored in AWS EU regions.
Security A web application firewall and DDoS protection at the network edge, per-asset access control lists and role-based access, secured APIs, and audit logging across the platform.
Backups and disaster recovery Automated backups with point-in-time recovery and built-in redundancy keep content safe, with automatic failover if part of the system goes down.
Caching Multi-layer caching and a CDN keep public sites fast under load, and precise cache invalidation means a change updates exactly the affected pages without a full purge.
Continuous improvement, zero downtime New features and fixes reach you as soon as they are ready, with no service interruption and no waiting for big quarterly release windows.
11 / Migration

A proven path off your old system

Lorien has a proven migration approach. Content has been migrated successfully from publishing systems such as Anygraaf Neo, Fiare Bold, and Naviga.

Feature Description
Run end to end Migrations are handled as in-house work from start to finish, covering planning, content conversion, loading, and validation. Media is migrated first, then articles and galleries follow with their references resolved, which keeps a large migration consistent.
Traceable Every migrated asset records its source system and external ID, so the result can be checked and a migration re-run if needed.

See how Lorien fits your newsroom

We will show you how Lorien plans, creates, and publishes across web, print, and every channel, and walk through how it would map to your titles and workflows.

Contact sales