Review of Crownpeak DXM
November 13, 2019

Review of Crownpeak DXM

Anonymous | TrustRadius Reviewer
Score 2 out of 10
Vetted Review
Verified User
Review Source

Overall Satisfaction with Crownpeak DXM

Our company is a digital agency that develops and maintains websites for many clients, and we use Crownpeak for websites with several of our clients. I'm not sure why Crownpeak is used other than that it's cloud-based and our company has a long history with it, so we have a partnership with Crownpeak.
  • The form inputs are very flexible
  • The REST API is generally pretty intuitive
  • It feels very top-to-bottom and self-contained, so I don't have to bother with lots of plugins and interop and such
  • Navigation within the folder structure feels clunky all-around.
  • Local debugging is difficult-to-impossible
  • The Visual Studio plugin is buggy
  • True documentation for the REST API is sparse
  • 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.
I bent the heck out of it to build a development framework for using it as a headless CMS. It was fun and the result has been pretty good. I haven't worked with any integrations. It would be very nice to be able to use third-party libraries in the template code.
We get pretty quick responses from our main support guy, but he frequently needs to forward the questions to the technical team, which can take much longer to get back to us.
From what I can gather from the conversations happening among more important people around me, it seems as if using Crownpeak makes sense for large enterprises when they wants a complete solution that includes hosting. From a developer perspective, the only reason I would suggest working with Crownpeak is that at least you get to use C#. None of the devs I know enjoy working with it overall, or feel like it helps them be as productive as they'd like to be.

Crownpeak DXM Feature Ratings

WYSIWYG editor
Code quality / cleanliness
Admin section
Page templates
Mobile optimization / responsive design
Publishing workflow
Form generator
Content taxonomy
SEO support
Bulk management
Availability / breadth of extensions
Internationalization / multi-language
Role-based user permissions

Crownpeak DXM Implementation

I don't know any exact timelines, but I think we've seen benefits from Crownpeak's SaaS architecture in getting websites up more quickly. If we had to deploy to either our own servers or a client's that would add an extra step of work that could definitely take a lot of time.