Hygraph (previously GraphCMS) is a native GraphQL Headless Content Management System (CMS) and now evolved as a Federated Content Platform, enabling teams across the world to unify, structure, enrich and distribute content from anywhere to anywhere.
$299
per month
Magnolia
Score 9.3 out of 10
Mid-Size Companies (51-1,000 employees)
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
Pricing
Hygraph
Magnolia
Editions & Modules
Professional
$299
per month per project
Scale
$899
per month per project
Enterprise
Custom
DX Core
$3500
per month
DX Cloud
$6000
per month
Offerings
Pricing Offerings
Hygraph
Magnolia
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
35% discount for annual pricing.
—
More Pricing Information
Community Pulse
Hygraph
Magnolia
Features
Hygraph
Magnolia
Hybrid CMS
Comparison of Hybrid CMS features of Product A and Product B
Hygraph
8.7
1 Ratings
0% above category average
Magnolia
-
Ratings
Collaborative editing
8.01 Ratings
00 Ratings
Content templates
10.01 Ratings
00 Ratings
Approval and authoring workflows
8.01 Ratings
00 Ratings
Security
Comparison of Security features of Product A and Product B
Hygraph
-
Ratings
Magnolia
8.0
69 Ratings
3% below category average
Role-based user permissions
00 Ratings
8.069 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Hygraph
-
Ratings
Magnolia
8.0
68 Ratings
3% above category average
API
00 Ratings
8.561 Ratings
Internationalization / multi-language
00 Ratings
7.661 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Hygraph
-
Ratings
Magnolia
8.0
74 Ratings
3% above category average
WYSIWYG editor
00 Ratings
8.565 Ratings
Code quality / cleanliness
00 Ratings
8.465 Ratings
Admin section
00 Ratings
8.070 Ratings
Page templates
00 Ratings
8.972 Ratings
Library of website themes
00 Ratings
7.01 Ratings
Mobile optimization / responsive design
00 Ratings
8.563 Ratings
Publishing workflow
00 Ratings
7.573 Ratings
Form generator
00 Ratings
7.058 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
I would recommend GraphCMS to anyone who is also using Gatsby to build their website. If not, I would recommend them to consider GraphCMS but also consider other options. GraphCMS is a tool in which you are responsible to make the most out of it, but sometimes this requires more time and knowledge than a normal engineer may be able to handle. But with more time and attention, the reward of off-lifting content creation from the developers is a huge time saver in the long run.
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.
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.
GraphCMS is very expensive at the enterprise level.
GraphCMS requires deep knowledge of the system and requires lots of time to be efficient with it (especially around creating specific data patterns/relationships).
Multiple times a day, the system will give us errors when attempting to save something but the errors are unclear as to what went wrong (can be irritating).
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.
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.
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.
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
We picked GraphCMS since it used Graph API and easily integrated it into our Gatsby website. It was also cheap (free) and easy to test out the product, making it easier to prove to our company we should pay for the product in the long run. Lastly, it seems to have a bunch of support from other developers which makes us confident will be around for a while (and we won't need to replace it anytime soon). Note: I also looked at Directus and DatoCMS but these were not options within TrustRadius
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.
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.