Ibexa, headquartered in Oslo, helps B2B companies to stay relevant and succeed by transforming traditional sales strategies into frictionless buying experiences, with their eponymous digial experience platform (DXP).
$20,143.81
per year
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
Ibexa DXP
Magnolia
Editions & Modules
Ibexa Content - Bronze
€ 15,000
per year
Ibexa Experience - Bronze
€ 23,000
per year
Ibexa Content - Silver
€26,000
per year
Ibexa Commerce - Bronze
€ 30,000
per year
Ibexa Content - Gold
€37,000
per year
Ibexa Experience - Silver
€40,000
per year
Ibexa Content - Platinum
€50,000
per year
Ibexa Commerce - Silver
€52,000
per year
Ibexa Experience - Gold
€57,000
per year
Ibexa Commerce - Gold
€74,000
per year
Ibexa Experience - Platinum
€77,000
per year
Ibexa Commerce - Platinum
€100,000
per year
DX Core
$3500
per month
DX Cloud
$6000
per month
Offerings
Pricing Offerings
Ibexa DXP
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
—
—
More Pricing Information
Community Pulse
Ibexa DXP
Magnolia
Features
Ibexa DXP
Magnolia
Security
Comparison of Security features of Product A and Product B
Ibexa DXP
9.0
1 Ratings
8% above category average
Magnolia
8.0
69 Ratings
3% below category average
Role-based user permissions
9.01 Ratings
8.069 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Ibexa DXP
8.0
1 Ratings
3% below category average
Magnolia
8.0
68 Ratings
3% above category average
API
7.01 Ratings
8.561 Ratings
Internationalization / multi-language
9.01 Ratings
7.661 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Ibexa DXP
5.4
1 Ratings
31% below category average
Magnolia
8.0
74 Ratings
3% above category average
WYSIWYG editor
7.01 Ratings
8.565 Ratings
Code quality / cleanliness
5.01 Ratings
8.465 Ratings
Admin section
7.01 Ratings
8.070 Ratings
Page templates
3.01 Ratings
8.972 Ratings
Library of website themes
2.01 Ratings
7.01 Ratings
Publishing workflow
8.01 Ratings
7.573 Ratings
Form generator
6.01 Ratings
7.058 Ratings
Mobile optimization / responsive design
00 Ratings
8.563 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
Ibexa DXP
5.6
1 Ratings
21% below category average
Magnolia
7.5
69 Ratings
1% above category average
Content taxonomy
9.01 Ratings
7.663 Ratings
SEO support
5.01 Ratings
7.163 Ratings
Bulk management
2.01 Ratings
7.757 Ratings
Availability / breadth of extensions
6.01 Ratings
8.062 Ratings
Community / comment management
6.01 Ratings
6.951 Ratings
Best Alternatives
Ibexa DXP
Magnolia
Small Businesses
Bloomreach - The Agentic Platform for Personalization
I always recommend Ibexa DXP to my fellows. The only scenario that I would not recommend it is if the site is either too small, too simple, or that they simply cannot afford to stand it up properly.
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.
Content Taxonomy: Content is managed in a tree. Though taxonomy vs folksonomy is a near-religious debate among professionals, clients seeing the system for the first time just seem to "get it" more often.
Content Flexibility: Common content types such as blog posts and articles are available out of the box. However, customizing these and creating new content types is very easy.
Developer Friendly: Developers need only a little PHP experience to get started. Of course being an expert doesn't hurt and opens the door for the development of custom modules.
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.
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.
It is quite easy to navigate through the backend and also, you can directly work in frontend view. Dynamic content can be created on the fly. Their Landing page features are awesome. You create a page by drag & drop.
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.
They are directly reachable and help you to deal with other services, e.g. if would like to set up a CDN for China or if you would like to integrate a tool like HubSpot. If there is anything you are missing, they help you to find a workaround until they can deliver such items - like local language versions.
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
eZ Publish isn't as large in community size and number of installations as other content management systems. However, it's just as capable and met our needs:
Developers, system administrators, and project manager can all speak the same language during the development and maintenance cycles of a site.
End-user training is very straight-forward.
Vendor support is available.
Client IT departments can access if need (developers/designers/sysadmins).
The community is there (forums) and there are solid contributions (extensions) from both the vendor and the community.
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.
We’ve priced other enterprise products and found Ibexa DXP to be a bit more expensive. However, not enough to dissuade us from staying with the product.
The partner ecosystem is small. However, we've worked with two Ibexa partners over the last 10 years. They were very skilled. They were great companies. We've interviewed other Ibexa partners in North America. We found them all to be professional with solid resumes.
Common knowledge: By making eZ a core offering, developers, system administrators, and project managers were able to communicate with each other effectively.
Training: Due to its content taxonomy, end-user training often went well.
Support: In our case, we had Gold support from eZ Publish which saved time and helped with customizations.
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.