Publish without code releases
Marketing and communications teams can update landing pages, posts, navigation, and campaign content without waiting for application deployments.
Vianordis--:--:-- UTCVianordis / ED. 02 / 2026
§ 07 — App support
Strukta
Governed content operations for sovereign digital teams.
Strukta helps regulated organizations publish multilingual websites, blogs, catalogues, and media libraries without handing content operations to a foreign SaaS platform.
01 — Problem
Content teams are stuck between slow releases and risky SaaS.
Marketing needs to publish fast. Product teams need structured catalogues. Compliance wants evidence. IT wants identity, storage, and auditability under its own control. Most CMS choices force a tradeoff between speed, governance, and sovereignty.
- Simple website changes still wait for developer release cycles.
- Pages, posts, products, and media live across disconnected tools.
- Global SaaS CMS platforms create residency, access, and vendor-lock concerns.
- Approvals, previews, SEO fields, and publishing history are hard to prove cleanly.
- Developers must integrate proprietary SDKs or rebuild content models by hand.
02 — Solution
Strukta gives editors speed and gives operators control.
Strukta combines a modern editorial workspace with a headless REST API and an included Next.js frontend. Editors manage localized content, media, navigation, homepage sections, posts, and products. Developers can feed the same content into websites, apps, portals, and other digital channels.
- Editorial teams publish pages, posts, products, and media from one governed workspace.
- Developers consume structured content through standard REST endpoints and generated TypeScript types.
- Administrators keep access tied to Keycloak SSO, role-based permissions, PostgreSQL, and EU-resident object storage.
03 — Benefits
Business outcomes before feature lists.
Strukta is designed for organizations that need content velocity without losing security, compliance posture, or infrastructure ownership.
Stay in control of data
Content records stay in PostgreSQL and media assets stay in EU-resident S3/Ceph storage operated under the Vianordis environment.
Reduce editorial risk
Drafts, previews, version history, scheduled publishing, and role boundaries give teams a cleaner path from idea to approved publication.
Serve many channels
Use the included frontend for websites or publish the same content through the REST API to portals, apps, and custom frontends.
Avoid CMS lock-in
Strukta is built on open foundations: Payload CMS, Next.js, PostgreSQL, S3-compatible storage, and standard HTTP APIs.
Fit regulated operations
SSO, RBAC, audit-friendly records, localization, and controlled storage make the CMS easier to align with governance processes.
04 — How it works
From draft to published channel in three steps.
- 01
Model and author
Choose pages, posts, products, media, navigation, or homepage content, then draft localized fields, reusable blocks, relationships, and SEO metadata.
- 02
Review and approve
Preview the page or content entry, check media, alt text, captions, URLs, and release timing, then route changes through the right editorial role.
- 03
Publish and reuse
Publish immediately or schedule the release, then serve the content through the built-in frontend or the headless REST API.
05 — Features
What teams can actually do in Strukta.
Page builder
Create hierarchical pages with hero, rich text, feature grid, and call-to-action blocks, plus templates and preview URLs.
Publishing desk
Manage blog posts, news, announcements, excerpts, featured images, related posts, categories, tags, and scheduled publication dates.
Product catalogue
Maintain product names, SKUs, pricing, currencies, images, specifications, categories, tags, related products, and SEO fields.
Media library
Store images, video, audio, and PDFs with alt text, captions, thumbnails, and responsive image sizes backed by S3-compatible storage.
Global site controls
Edit homepage content, main navigation, footer menus, mobile menus, site settings, social links, contact details, and analytics settings.
API access
Expose content through Payload REST routes with filtering, pagination, relationship queries, and standard HTTP clients.
06 — Architecture
Architecture and security model.
Strukta is built for teams that want the ergonomics of a modern CMS while keeping identity, storage, and runtime inside a controlled European platform.
- Keycloak OIDC maps users into cms-admin, cms-editor, cms-author, and cms-viewer roles.
- Payload CMS provides the admin UI, collection permissions, REST API, drafts, versions, and generated TypeScript types.
- PostgreSQL stores structured content in a dedicated CMS schema.
- S3-compatible Ceph storage keeps media assets in EU-resident object storage.
- Next.js renders the public frontend and can also serve Strukta as a headless-only backend.
- Kubernetes deployment supports rolling updates, probes, resource limits, and production operations.
07 — Use cases
Where Strukta fits.
Corporate websites
Give communications teams multilingual publishing control while IT keeps infrastructure and access policy centralized.
Product catalogues
Maintain structured product data once, then reuse it across websites, sales portals, and custom frontends.
News and announcements
Run controlled publishing workflows for posts, executive updates, customer notices, and public communications.
Regulated industries
Support healthcare, finance, education, and public-sector content programs where residency and governance matter.
Developer content APIs
Feed content into web apps, mobile apps, digital signage, portals, and internal tools through a standard REST interface.
08 — Integrations
Fits into the environment you already operate.
Strukta uses common infrastructure and identity components instead of forcing proprietary content-platform plumbing.
Keycloak
Keeps access tied to organization accounts, roles, and sign-in policy.
FreeIPA / LDAP
Shows how this service fits into the wider Vianordis environment instead of standing alone.
PostgreSQL
Stores structured service records in a controlled tenant-aware backend.
Ceph S3
Provides the governed place where service data and files are stored.
MinIO
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Next.js
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Payload REST API
Lets approved systems connect without ad hoc exports or manual copy-paste.
Kubernetes
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Matomo
Shows how this service fits into the wider Vianordis environment instead of standing alone.
Custom frontends
Shows how this service fits into the wider Vianordis environment instead of standing alone.
09 — Trust
Compliance and trust signals.
The product is designed to make content operations understandable to security, compliance, and operations teams.
Data residency
EU-hosted PostgreSQL and S3/Ceph storage.
Access control
Keycloak SSO with admin, editor, author, and viewer roles.
Auditability
Drafts, versions, timestamps, and role-gated collection access.
Encryption path
TLS in transit, encrypted database connections, and controlled object storage.
Operational model
Containerized Next.js/Payload app deployed on Kubernetes.
Open foundations
Payload CMS, Next.js, PostgreSQL, and S3-compatible storage.
10 — Pricing
Start with transparent pricing or a guided demo.
Strukta is listed on the published Vianordis rate card. For regulated teams, a demo is usually the fastest way to map collections, roles, migration paths, and hosting requirements.
11 — FAQ
Questions technical buyers usually ask.
Who is Strukta for?
Strukta is for marketing, product, communications, and publishing teams that need a governed CMS with strong IT ownership, not a black-box SaaS platform.
Can Strukta run as a headless CMS?
Yes. The Payload REST API exposes structured content to custom frontends, portals, applications, and other channels. The included Next.js frontend can be used when teams want a full-stack deployment.
Does it support multilingual content?
Yes. The current content model includes English, German, and French localization with fallback handling, and the collection fields are designed for localized publishing.
How is access controlled?
Strukta uses Keycloak OIDC and maps identity roles into admin, editor, author, and viewer permissions across users, pages, posts, products, tags, categories, and media.
Where are media assets stored?
Media is stored through S3-compatible storage. In the Vianordis environment, Strukta uses EU-resident Ceph object storage for uploaded images, video, audio, and PDFs.
Can existing content be migrated?
Yes. Strukta uses standard PostgreSQL and REST APIs, so migration can be planned from existing CMS exports, product catalogues, or structured content sources.
12 — Next step
Give content teams speed without surrendering control.
See how Strukta can replace scattered publishing tools with one governed CMS for multilingual sites, product content, media libraries, and API-fed experiences.