What is our primary use case?
Our main use case for WP Engine WordPress Digital Experience Platform was that we were using WordPress at the time, which is a previous tool or a previous suite, and we grew it into the next step of WP Engine WordPress Digital Experience Platform, which is the next step platform-wise for hosting our environments for our customers' front end SaaS support services requirements.
The other key thing about our main use case or how we use WP Engine WordPress Digital Experience Platform is that it allowed us to condense it into a single platform versus how we had originally set up WordPress over a distributed platform that had a lot more overhead, maintenance-wise, and this helped us cut down our overall manpower workloads as we work with the platform.
How has it helped my organization?
WP Engine WordPress Digital Experience Platform has positively impacted my organization because finally we have a tool that can go into infrastructure as a platform. That is a great value because with that we can basically adapt our learning curve. The learning curve, since we already knew WordPress, is lower for us in regards to bringing it over, but yet we have a product that could finally leave the server-based footprint and go into the infrastructure enterprise footprint cleanly and give us the ability to treat this as an infrastructure resource now.
Specific outcomes or metrics that show the positive impact of WP Engine WordPress Digital Experience Platform include improvements in efficiency because you scale it to a single platform that is scalable which is still a single platform. The cost savings is yet to be determined, but the improvements of management are clearly there. Plus, to scale from AWS to GCP or to do both together for a business continuity model is viable now and very important. When customers are getting these types of services, you have to have a system that performs better than simply falling back to a DR site. A business continuity model with WP Engine WordPress Digital Experience Platform services would continue to operate even if you lost whole data centers, which is important from an operations perspective.
What is most valuable?
The best features WP Engine WordPress Digital Experience Platform offers include consolidation, working toward automation with DevOps, and reducing the man-hour workloads while still offering a very flexible front end that follows the wiki strategies of WordPress, alongside offering content management and documentation support as well as the extended consolidated dashing or dashboard setup.
Out of those features, the one I think has had the biggest impact on my team is the reduction in maintenance time at the operations team level, as my team felt good that they did not have to work so much to maintain the environment, reducing it from an 18-hour window per year down to a four-hour window per year. That does add up when you add up every individual platform and helps reduce some of the operational stress in the environment. Furthermore, from the customer base perspective, they now had a front end with the ability of introduction wiki functionality for documentation and content management, which is that next logical step to go into in regards to working with AI, API calls, and background processing.
What needs improvement?
To improve WP Engine WordPress Digital Experience Platform, a crucial value would be that it has the ability to provide asynchronous or synchronous data synchronization with an alternate cloud provider location as part of its platform and/or a DR site. The principle right now is we are forced to use a backup and then that backup is restored in a DR environment and do a restore. It would be more efficient for us, as I stated earlier, using a business continuity model to have another platform at our DR site that runs alongside our production WP Engine WordPress Digital Experience Platform site and is asynchronously synchronizing its data over on a constant basis. Thus, there is no loss of data, just a redirection of who is going to handle the data until the production environment is restored, which I think is a real value-add and crucial.
Another important aspect is better integration with DevOps and automation. Regarding needed improvements for WP Engine WordPress Digital Experience Platform, I think there are grounds for WordPress to offer something called WebOps. WebOps is not your product, but more of a dashboard for all related web platforms. WP Engine WordPress Digital Experience Platform would be a decent platform to consider this for because managing websites is an ongoing issue. When the customer is using WordPress for its front end, you could have hundreds of those websites out there needing management, and it would be beneficial to see a more consolidated approach. It does not matter what type of website web setup you have out there, but a collective WebOps that is agnostic of all products yet can support the websites and their telemetry and analyses would be great.
For how long have I used the solution?
I have been using this solution for about four years.
What do I think about the stability of the solution?
WP Engine WordPress Digital Experience Platform is stable.
What do I think about the scalability of the solution?
The scalability of WP Engine WordPress Digital Experience Platform is limited. It could be improved, but it functions to a degree.
How are customer service and support?
Customer support for WP Engine WordPress Digital Experience Platform is good. Customer service was fine, and I had no issues with customer service.
Which solution did I use previously and why did I switch?
We previously used a different solution, specifically basic web services, Apache web services to be specific. There was not a suite or platform like WordPress at that time several years ago, which became quite complicated, involving a lot of overhead and divested time in operations versus productivity. We had to get to a solution that could begin that process, starting with WordPress itself and evolving into this product, which helped us and justified why we switched to a more consolidated platform.
What was our ROI?
I have seen a return on investment because it helped reduce our personnel requirements, and the money saved was accomplished.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for WP Engine WordPress Digital Experience Platform is that it is pretty basic, pretty straightforward, quick, efficient, and functional.
Which other solutions did I evaluate?
I was not present during the evaluations of other options, but I do know they eventually led to the use of WordPress.
What other advice do I have?
My advice to others looking into using WP Engine WordPress Digital Experience Platform is that one of the most important things about any platform is to ensure that your core web code, which you plan to use, if it is HTTPS and so on, XML and other functionalities are reviewed tightly with the support components of a platform like WP Engine. This evaluation is where the problems will arise, and compatibility will be a driving force behind that. You want to be very careful to consider these evaluations to make sure that it meets your requirements. You do not want to have a tool that has features that can never be used because of the stack code in your web software and how your websites are set up. Therefore, you need a 100% match for this tool to be fully effective for your objectives.
Regarding WP Engine WordPress Digital Experience Platform's AI capabilities, the governance and security compliance requirements were and are handled outside of WP Engine WordPress Digital Experience Platform process. Our SecOps are driven by the protocols used by this tool, not the tool itself. We adhere to the best recommendations of the WordPress company about their internal security requirements that should be applied or best practices that should be upheld, but the governance and security of our environment is holistic and not specific to WordPress itself.
The accuracy and reliability of output from WP Engine WordPress Digital Experience Platform's AI capabilities are still being developed and are not quite there yet, capabilities-wise, but the beginnings look promising. We know that there is still more needed because no vendor out there has their AI fully integrated, which means the AI is working within the subpart subfunctions of the tool itself yet, but it is getting there, and looking really good.
WP Engine WordPress Digital Experience Platform is deployed in my organization in the cloud. In this case, we use AWS as our cloud provider. I purchased WP Engine WordPress Digital Experience Platform through the AWS Marketplace. I do not think there are any other improvements needed for WP Engine WordPress Digital Experience Platform that we have not discussed. I would rate this solution a 7 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)