Founded in Switzerland in 1997, Magnolia is a CMS used to build composable digital experiences. Magnolia helps create fully integrated customer experiences and speeds up digital delivery of content. Magnolia boasts 480 enterprise customers, thousands of Community Edition deployments, and more than 200 certified Magnolia Partners around the world. They further state that their enterprise customers include Sanofi, Generali, the Atlassian, The New York Times, Harley Davidson, and Union…
$3,500
per month
Webflow
Score 8.6 out of 10
N/A
Webflow is a Website Experience Platform for modern marketing teams, used to visually build, manage, and optimize websites that offer both the consumer experience teams expect and enterprise-grade performance and scale.
$18
per month
Pricing
Magnolia
Webflow
Editions & Modules
DX Core
$3500
per month
DX Cloud
$6000
per month
Basic
$18
per month
CMS
$29
per month
Ecommerce - Standard
$42
per month
Business
$49
per month
Ecommerce - Plus
$84
per month
Ecommerce - Advanced
$235
per month
Offerings
Pricing Offerings
Magnolia
Webflow
Free Trial
Yes
Yes
Free/Freemium Version
No
Yes
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
Up to a 22% discount available for annual pricing.
More Pricing Information
Community Pulse
Magnolia
Webflow
Features
Magnolia
Webflow
Security
Comparison of Security features of Product A and Product B
Magnolia
8.0
69 Ratings
3% below category average
Webflow
7.8
16 Ratings
5% below category average
Role-based user permissions
8.069 Ratings
7.816 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Magnolia
8.0
68 Ratings
3% above category average
Webflow
8.2
13 Ratings
6% above category average
API
8.561 Ratings
8.113 Ratings
Internationalization / multi-language
7.661 Ratings
8.311 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Magnolia
8.0
74 Ratings
3% above category average
Webflow
8.1
19 Ratings
4% above category average
WYSIWYG editor
8.565 Ratings
8.119 Ratings
Code quality / cleanliness
8.465 Ratings
8.518 Ratings
Admin section
8.070 Ratings
7.019 Ratings
Page templates
8.972 Ratings
8.418 Ratings
Library of website themes
7.01 Ratings
8.315 Ratings
Mobile optimization / responsive design
8.563 Ratings
9.519 Ratings
Publishing workflow
7.573 Ratings
8.418 Ratings
Form generator
7.058 Ratings
7.015 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Magnolia is a very capable DXP, that provides client with lots of flexibility in composing its own stack. While the core of the platform is a content management system, the open architecture of Magnolia DXP allows it to connect to any platform, allowing client to extend the capabilities. One scenario would be a centralized content hub - where through a single platform, content authors can choose which channel to distribute what content. For example, long form content for consumers viewing on a laptop, short form content for those using a mobile browser. This allow the client to personalized the experience based on channels. Another scenarios would be leveraging on GenAI - using Magnolia's built-in connector to ChatGPT. If that is not the service that one desire, you can always connect to another AI service such as Google Gemini. With GenAI, connected, content author can use AI as co-pilot to help them scale up their content production.
Since the purpose in my case is to build a small professional looking site to present project outcomes and other research, I can create custom fields and design experimentations. Webflow builds sites that are super professional, with many amazing templates that don't look cheap. Additionally, I can test responsive layouts. Apart from this, I used 1-2 static pages to illustrate key findings for example what a multilingual site could look like with screenshots without needing CMS in free version, which are all the valuable skills to acquire. Compared to WordPress, Webflow is expensive with limited free features, although it has really cool additional features that will make the site I build stand out.
Speed of development - time to delivery from zero to MVP was excellent
Ease of use - the authoring experience is very easy to build and train
PAAS/SAAS - the managed service platform removed the traditional overhead of running in-house technologies, meaning we could focus on value add, with less time spent keeping the lights on.
Saves time- because I don't have to do double entry of content.
It saves money. I like that it is an all-in-one system, so I don't have to host elsewhere.
Flexibility - Webflow provides me with a lot of flexibility in my webpage design, allowing me to adjust pages as needed, depending on the content types.
The documentation provides samples that are often out of context, and difficult to know where the provided example code should be implemented. More tutorials providing the full project or step-by-step instructions on how to implement subject material would help greatly. Baeldung is a resource I would consider the gold standard in how this is done in other spaces.
The use of JCR and Nodes makes object serialization/deserialization painful. Jackson compatibility or similar would be a welcome enhancement to the developer experience. Maybe leveraging code-gen from light modules to build model classes when possible could help accomplish this.
Modifying the home layout from light modules is frustrating. It seems that any configuration overrides made merge with the default rather than overwriting, which makes for a difficult combination of guess-and-check while referencing the documentation to see what should be in each row/column when making changes.
Including "mark all as read" or "delete all" in the notifications app would be a great quality of life improvement. It seems that by default, users have to individually select messages and operate them.
Brand recognition is still behind WordPress, which can make it a challenging sell for clients looking to play it safe in their CMS decision.
The CMS is ideal for smaller datasets, but higher content sites introduce some minor challenges.
Alignment between designers and developers is key prior to implementation. The flexibility of the platform requires careful planning to avoid over-engineering.
We've shown it to a number of users both clients and our own team and despite initial apprehensions, they "get it" very quickly. It's intuitive and friendly and quick to perform daily tasks. We once had a client tell us "Using Magnolia makes me smile" which says it all for us.
Webflow is very easy for a beginner to get started with and achieve good results, but to achieve an expert level of understanding requires experience and some web development knowledge. HTML5, CSS3 and JavaScript knowledge aren't required to use Webflow, but an expert will know BEM class naming patterns, be able to create reusable elements and design systems, and add 3rd party integrations that require custom code.
In my experience, their customer service is an absolute joke, I tried reaching out to them they took forever. I had to keep following up with them as if they never received it in the first place. It’s a new platform, so guidance is needed. Tried the university they offer, in my opinion, it is completely useless, I would just completely move on from this website.
I gave [it] 7/10 only because of the loading time of pages. Otherwise, I think it deserves an 8. Normally this is not an issue per [se] but considering the rating matrix and as I have been asked to honestly write about it. Yes, the page loading times could be improved.
In my opinion, it is horrible, the rendering takes forever. I have the newest MacBook and the platform will still lag and slow down on me. I’m not a developer, I am a designer which makes it worst because I am using the features they are providing not extra coding features. In my opinion, it is a horrible platform really, stay away.
You always get an answer based on your SLA. But you always get a solution. That's the successfactor in this case. To often i was frustrated about people in a company without even a clue what there product is about or how to solve a problem. Magnolia's Support Team does a very good job and try to help you in most of the cases
I haven't had to engage them from a support perspective; however, there is a considerable user community for tips/ideas/troubleshooting and the like. I believe the Pro plan supports additional resources but we didn't find that the cost justified the outcome. Overall the need for support has been relatively minor.
I've used several CMSs like AEM and EpiServer, and comparatively, they all excel at different things. Magnolia is the best to develop for/against. Episerver has the best/most fluid UI in terms of content editing, and the overall admin experience AEM is just all around sucks.
A lot more design control and easier to create a custom site, and then also to scale that site going forward. There's a lot about WordPress I miss, though, when it comes to managing a blog—user permissions, SEO control, edit HTML version of posts.
I feel it doesn’t perform the way it’s supposed to and it doesn’t have any beneficial factors to it. In my opinion, there is no reason to use a platform like this when Wix and Shopify, and WordPress exist. I believe Webflow is a platform that shouldn’t exist and it’s only popular because of the hype it received. I tried it and hate it completely.
Magnolia has brought about positive impacts. For instance, we need not outsource web design and marketing services because thanks to this software, we can handle most work inhouse
The software is affordable with no compromises on capabilities and therefore it is gives us value for money.