Content platforms, with impartial advice.
We work with Magnolia, Strapi, Contentful and Liferay. Which platform fits is decided by your requirements, not by our preference.
Four platforms side by side
| Kriterium | Magnolia | Strapi | Contentful | Liferay |
|---|---|---|---|---|
| Operation | On-premises or cloud | Self-hosted or Strapi Cloud | SaaS, fully managed | On-premises or PaaS |
| License | Community or Enterprise Edition | Community Edition free of charge (MIT) | Subscription | Free Edition or subscription |
| Technology | Java | Node.js, TypeScript | API-first | Java, OSGi |
| Strength | Editorial control, visual SPA editor, multi-site | Full data control, freely customizable | Large editorial teams, workflows, SOC 2 | Roles and permissions, SSO, self-service |
| Best for | Brand presence across many channels | Custom projects with an in-house development team | Global multi-site without own infrastructure | Intranet, extranet, customer portal |
Magnolia: enterprise CMS built on Java
Traditional page-based, purely headless via the delivery APIs, or hybrid. Current projects run on Magnolia 6.4; we continue to support older 6.x systems and upgrade them when needed.
Official partner profile →Strapi and Contentful: maintain content once, deliver it everywhere
Content is stored centrally and delivered via API to the website, apps and other channels. We support you with platform choice, content model and frontend.
One process for all three platforms
-
01Initial callUse case, channels, editorial team and system landscape. Free of charge, about 60 minutes.
-
02Platform choice and architectureMagnolia, Strapi or Contentful; traditional, hybrid or headless.
-
03Content modelContent types, relations and roles as the basis for templates and frontend.
-
04Delivery in sprintsTemplates or frontend, integrations, content migration, regular demos.
-
05Go-live and handoverDeployment, editor training, documentation. Operations on request.
“In headless projects, the content model is the most important step. Thinking the content structure through early saves effort later, whatever the platform.”
Magnolia and headless CMS
Magnolia, Strapi, Contentful or Liferay: which platform fits?
It depends on the use case. Magnolia suits brand presences across many channels, Strapi custom projects with an in-house development team, Contentful global multi-site without own infrastructure, and Liferay intranets, extranets and customer portals.
Is Portalworks a Magnolia partner?
Yes. Portalworks is a Magnolia Solution Partner for implementation and integration and is listed in Magnolia’s partner directory.
What does headless CMS mean?
Content is maintained centrally and delivered via APIs such as REST or GraphQL to the website, apps and other channels. A separate frontend, for example built with React, Next.js or Vue, handles the presentation.
Can Strapi be hosted in Germany?
Yes. Strapi is open source; the Community Edition is MIT-licensed and can be self-hosted, including with a hosting provider in Germany.
Does Portalworks migrate existing websites to Magnolia or a headless CMS?
Yes, from TYPO3 and WordPress among others. This includes content mapping, preserving URLs and search rankings and, if needed, running both systems in parallel.
Magnolia, Strapi or Contentful?
Initial call with Marc Hermann. We get back to you within 24 hours.