Crownpeak CMS is a composable, enterprise-ready content management system that empowers global teams to seamlessly orchestrate personalized digital experiences across all content channels. Marketing teams can create, manage, and monitor inclusive, accessible, and transactional experiences fast without compromising on functionality, security, or service.
N/A
Drupal
Score 8.2 out of 10
N/A
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
Pricing
Crownpeak CMS
Drupal
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Crownpeak CMS
Drupal
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Crownpeak CMS
Drupal
Considered Both Products
Crownpeak CMS
Verified User
Director
Chose Crownpeak CMS
Crownpeak is the only true SAAS CMS on the market. All the others are either not/partially SAAS or providing it through other 3rd party vendors.
CrownPeak’s DQM gives the entire CrownPeak suite a slight advantage because it’s so helpful in tracking functionality issues, typos and areas for SEO improvements.
The other competitive products I used had not had these features in such a robust way the last time I used them …
Crownpeak DXM is a great solution if you are looking for a flexible platform that allows engineers to quickly develop while also making it easy for content authors to work especially in scenarios where you need multi-language support. It is also good for scenarios where you want a cloud-based solution and are looking for just one vendor to handle hosting and offer the CMS.
Well, I'm definitely biased, I've been working with Drupal for 12+ years, and I can say it's appropriate for any size/scale of a project, whether it's a small catalog website or a huge corporation. If I want to dial it down to a specific use case, Drupal is best what most customers/clients that have high-security standards, and need to have extensive editorial experience and control over their website's architecture. Due to its core design, Drupal can connect with each part of its own and any external third-party resources quite easily. For a less-suited scenario, I might say that if you don't have enough budget to get proper work done, sometimes just using WordPress with a pre-designed theme might sound better to you, but if you have the budget and the time, always go with Drupal
Build & manage digital experiences without dependency on your IT team
Built-in Digital Quality tool (DQM) tool allows you to check the quality of content and any accessibility issues and immediately flag any issues before publishing.
Build websites with the component-based technology and spend less effort in creating the best user experience for the end-user
Content Types... these are amazing. Whereas a more simplistic CMS like Wordpress will basically allow you to make posts and build pages, Drupal 8 gives you the ability to define different types of content that behave differently, and are served up differently in different areas of the website.
Extensibility... it scales, ohhhh does it scale. They've really figured out server-side caching, and it makes all the difference. Once a page has been cached, it's available instantly to all users worldwide; and when coupled with AWS, global redundancy and localization mean that no matter where you're accessing the site, it always loads fast and crisp.
Workflows... you have the ability to define very specific roles and/or user-based editorial workflows, allowing for as many touchpoints and reviews between content creation and publication as you'll require.
Crownpeak moved to a web browser admin tool in 2018, which has made the admin experience much better, but there are still a couple of features missing from the browser version that won't arrive until later in 2019.
Integration with 3rd party digital asset management tools would be great.
Smoother integration with source control would be nice.
Security and new release notifications are a hassle as they happen too often
Allowing them to write PHP modules is a big advantage, but sometimes integrating them is a small challenge due to the version the developer is working on.
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.
Crownpeak DXM is a flexible easy to use CMS platform speaking to the most challenging localization scenarios. Crownpeak users have the freedom to integrate DXM platform with their existing technology at no cost. Moving from legacy systems to the Saas platform is painless and cost-effective. Extensive targeting and personalization options are something that users will benefit from.
It's a great CMS platform and there are a ton of plugins to add some serious functionality, but the security updates are too complex to implement and considering the complexity of the platform, security updates are a must. I don't want my site breached because they make it too difficult to keep it up to date.
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).
Pages load very fast on production (assuming you develop with basic SEO practices in place) due to Crownpeak's publishing architecture. The slide downside is that publishing can be a bit slow at times.
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.
Crownpeak DXM's service and support are outstanding. We have immediate access to both the tech support team and the software engineering team. We can get a support person on the phone whenever needed, and we can schedule impromptu training sessions at any time. Best support I have ever received from a platform provider in 20 years of software and application development.
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.
We received on-site training from Crownpeak, the trainer had touched upon every possible scenario and provided great insights about the product & ease of implementation.
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.
My team left training with a solid understanding of how to use the product and the developer training ended with a test to ensure the ability to properly develop was learned properly. Recently, Crownpeak has added a self-paced training option which makes it extremely flexible to on-board new developers.
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.
SaaS model is perfect for us to avoid slow and costly version updates to get access to new features and functions. Crownpeak is a true SaaS model, so we get all the good new stuff without the need to invest in effort, time or money. this frees our teams to focus on content creation and deployment, which is pretty fast because the DXM publishes straight to html through the headless model.
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%
I was not at this team within my organization during the evaluation period of Crownpeak. However, my previous team used Sitecore. Crownpeak is a bit easier to use from a UI perspective and has more creative options within the tool. Sitecore's clunky UI also was a reason I found out later why we ended up using Crownpeak as our DXM.
Drupal is community-backed making it more accessible and growing at a faster rate than Sitefinity which is a proprietary product built on .NET. Drupal is PHP-based using some but not all Symphony codebase. Updates for Drupal are frequent and so are feature adds.
In some recent projects we have delivered to our clients, we were able to roll out sites in shorter time period due the scalability of the Crownpeak's DXM solution.
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.
I'm pretty sure it raises our back-end development costs by making the development process (of creating input forms and producing outputs from the content) more complicated and painful than it needs to be.
It helps lock our clients in to us because not a whole lot of agencies have Crownpeak expertise.
It helps our clients not have to deal with their own IT teams, which they tend to dislike working with.
Drupal has allowed us to build up a library of code and base sites we can reuse to save time which has increased our efficiency and thus had a positive financial impact.
Drupal has allowed us to take on projects we otherwise would not have been able to, having a further impact.
Drupal has allowed us to build great solutions for our clients which give them an excellent ROI.
