Drupal is a free, open-source content management system written in PHP that competes primarily with Joomla and Plone. The standard release of Drupal, known as Drupal core, contains basic features such as account and menu management, RSS feeds, page layout customization, and system administration.
N/A
Ibexa DXP
Score 8.1 out of 10
N/A
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
TYPO3
Score 8.0 out of 10
N/A
TYPO3 CMS is an open source web content management system with a global community, backed by the approximately 900 members of the TYPO3 Association.
$0
Pricing
Drupal
Ibexa DXP
TYPO3
Editions & Modules
No answers on this topic
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
No answers on this topic
Offerings
Pricing Offerings
Drupal
Ibexa DXP
TYPO3
Free Trial
No
No
No
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
Drupal
Ibexa DXP
TYPO3
Features
Drupal
Ibexa DXP
TYPO3
Security
Comparison of Security features of Product A and Product B
Drupal
8.1
74 Ratings
1% below category average
Ibexa DXP
9.0
1 Ratings
10% above category average
TYPO3
-
Ratings
Role-based user permissions
8.174 Ratings
9.01 Ratings
00 Ratings
Platform & Infrastructure
Comparison of Platform & Infrastructure features of Product A and Product B
Drupal
7.7
69 Ratings
1% below category average
Ibexa DXP
8.0
1 Ratings
1% below category average
TYPO3
-
Ratings
API
7.264 Ratings
7.01 Ratings
00 Ratings
Internationalization / multi-language
8.160 Ratings
9.01 Ratings
00 Ratings
Web Content Creation
Comparison of Web Content Creation features of Product A and Product B
Drupal
6.5
78 Ratings
18% below category average
Ibexa DXP
5.4
1 Ratings
28% below category average
TYPO3
-
Ratings
WYSIWYG editor
6.271 Ratings
7.01 Ratings
00 Ratings
Code quality / cleanliness
8.175 Ratings
5.01 Ratings
00 Ratings
Admin section
6.878 Ratings
7.01 Ratings
00 Ratings
Page templates
5.577 Ratings
3.01 Ratings
00 Ratings
Library of website themes
5.568 Ratings
2.01 Ratings
00 Ratings
Mobile optimization / responsive design
6.572 Ratings
00 Ratings
00 Ratings
Publishing workflow
6.776 Ratings
8.01 Ratings
00 Ratings
Form generator
6.472 Ratings
6.01 Ratings
00 Ratings
Web Content Management
Comparison of Web Content Management features of Product A and Product B
If you want to set up a basic Not For Profit (NFP) Membership system and content base, Word Press is easier than Drupal. However, if you have specific needs that require a fair bit of customisation then Drupal is the best CRM available. If the webmaster is confident with PHP and SQL, Drupal allows a lot of creativity.
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.
TYPO3 is great if you need to connect some systems in company to work together: like ecommerce + CRM + ERP + MRP and build an Extranet for partners/dealers where they can order your products, see particular BOM (bill of material), paid/unpaid invoices and use email marketing on top of it. You can do it but keep in mind that you will need a dedicated hosting, well organized admin(s) and some handwritten code. For simple blog TYPO3 is also a good choose, but WP would be better I think.
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.
This is not an easy CMS to work with if you don't have a good understanding of website development. It isn't "plug-and-play" like Wordpress or Shopify.
Over time, doing major updates to the system can be taxing, especially if you aren't well-versed enough in doing system updates in line with your "child" theme and code.
The CMS can become somewhat cumbersome with server resources if not carefully optimized while you build and customize it to your liking.
compared do Wordpress - far less community support
when you run a simple blog - it is simple as piece of cake. But if it is a large news site, with many user roles, extensions and permissions - it may be hard to find an admin that will organize and keep that stuff working.
server resources: so you want performance and speed with all that modules enabled? make sure that you have dedicated server in most cases. WP works much better here.
The time and money invested into this platform were too great to discontinue it at this point. I'm sure it will be in use for a while. We have also spent time training many employees how to use it. All of these things add up to quite an investment in the product. Lastly, it basically fulfills what we need our intranet site to do.
As a team, we found Drupal to be highly customizable and flexible, allowing our development team to go to great lengths to develop desired functionalities. It can be used as a solution for all types of web projects. It comes with a robust admin interface that provides greater flexibility once the user gets acquainted with the system.
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.
Drupal itself does not tend to have bugs that cause sporadic outages. When deployed on a well-configured LAMP stack, deployment and maintenance problems are minimal, and in general no exotic tuning or configuration is required. For highest uptime, putting a caching proxy like Varnish in front of Drupal (or a CDN that supports dynamic applications).
Drupal page loads can be slow, as a great many database calls may be required to generate a page. It is highly recommended to use caching systems, both built-in and external to lessen such database loads and improve performance. I haven't had any problems with behind-the-scenes integrations with external systems.
As noted earlier, the support of the community can be rather variable, with some modules attracting more attraction and action in their issue queues, but overall, the development community for Drupal is second to none. It probably the single greatest aspect of being involved in this open-source project.
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.
I was part of the team that conducted the training. Our training was fine, but we could have been better informed on Drupal before we started providing it. If we did not have answers to tough questions, we had more technical staff we could consult with. We did provide hands-on practice time for the learners, which I would always recommend. That is where the best learning occurred.
The on-line training was not as ideal as the face-to-face training. It was done remotely and only allowed for the trainers to present information to the learners and demonstrate the platform online. There was not a good way to allow for the learners to practice, ask questions and have them answered all in the same session.
Plan ahead as much you can. You really need to know how to build what you want with the modules available to you, or that you might need to code yourself, in order to make the best use of Drupal. I recommend you analyze the most technically difficult workflows and other aspects of your implementation, and try building some test versions of those first. Get feedback from stakeholders early and often, because you can easily find yourself in a situation where your implementation does 90% of what you want, but, due to something you didn't plan for, foresee, or know about, there's no feasible way to get past the last 10%
Drupal can be more complex to learn, but it offers a much wider range of applications. Drupal’s front and backend can be customized from design to functionality to allow for a wide range of uses. If someone wants to create something more complex than a simple site or blog, Drupal can be an amazing asset to have at hand.
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.
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.
Drupal is well known to be scalable, although it requires solid knowledge of MySQL best practices, caching mechanisms, and other server-level best practices. I have never personally dealt with an especially large site, so I can speak well to the issues associated with Drupal scaling.
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.