Where can I deploy Entando?
Entando can deploy to a private cloud, public cloud, or on the local infrastructure that makes sense for your use case. Entando provides out-of-the-box deployment on AWS and Azure using Kubernetes. Entando also provides images and documentation for deploying on OpenShift. Additionally, we provide Docker images, extendable base Docker files, and examples that use Docker Source-to-Image (S2I). In most cases, including the cloud cases above, Entando is deployed in a J2EE container like JBoss EAP, Wildfly, or Tomcat.
Do you support high availability (HA) architecture?
Yes, Entando supports an HA architecture.
What is the Entando Component Repository?
The Entando Component Repository allows you to automatically install your Entando components for quick reuse in all of your Entando applications.
Will I be competing against Entando direct sales people and/or other partners?
No. Entando sales accounts are incentivized to help you be successful. We will hold periodic pipeline calls with you to understand your roadmap and what help you need.
What are the marketing & sales benefits of becoming an Entando partner?
Entando provides all the support needed to introduce and promote our micro frontend platform, from communication materials to co-marketing efforts. Other forms of support vary according to the level of engagement. Nevertheless, in every case, we aim for the highest levels of collaboration and visibility opportunities.
How can I migrate from one version of Entando to the next?
Every migration is different. As a platform, Entando allows our users and customers to build their own software and so there will be migration considerations for the Entando components of an architecture as well as the customer-developed components. Migrating the core elements of the architecture to a new version should be relatively straightforward.