Choosing the Hadrone PPM software usage model (On-Premises or SaaS) is crucial for the Customer, as it affects the responsibilities of both the Customer and the Contractor, as well as security, operational continuity, and system performance.

We offer both options – the Hadrone PPM software is built to be used either in the cloud or on the customer's own infrastructure. It is also possible to switch between the two models, ensuring seamless operations and no loss of project data.

Therefore, it cannot be said that one model is better or worse than the other. Both models work well, depending on the needs and conditions of the organization.

On-Premises model

The On-Premises model means that the Customer purchases a license for the Hadrone PPM software and installs it on their own IT infrastructure (using their physical or virtual servers, their database, storage, and backup system). Access to the software is still through a web browser, so user does not install anything on their computer.

In this model, our role is to deliver the Hadrone PPM installation package along with installation documentation. Sometimes, we are also involved in providing support during the installation. However, the responsibility for maintaining the software, including updating it to new versions, lies with the Customer. The Customer is also responsible for the security, continuity of operations and performance of their IT infrastructure.

When to choose Hadrone PPM software in the On-Premises model? Below are a few arguments in favor of this solution:

  • the software is recommended according to internal security procedures or external (legal) regulations,
  • integration of Hadrone PPM with other systems is planned, and these systems cannot communicate with the cloud,
  • the organization has its own IT infrastructure and a maintenance team, and generally prefers using software hosted internally.

SaaS model

The SaaS model means that the Customer does not purchase a license for the software but instead subscribes to a service that provides access to the software in the Contractor's cloud. This model is also supported by Hadrone PPM. In this case, the software is hosted in our cloud on MS Azure, within the EEA region (due to GDPR requirements).

In this model, the Customer only uses the software – all maintenance tasks, including updates to new versions of the software, ensuring proper security, continuity of operations, and performance, are handled by us. Our cloud solutions have been proven at scale, so we can guarantee a high level of service and can scale flexibly as the number of users grows.

When to choose Hadrone PPM software in the SaaS model? Below are a few arguments in favor of this solution:

  • the software is recommended within the IT strategy,
  • there is no plan to integrate Hadrone PPM with systems that cannot communicate with the cloud,
  • the organization does not have IT infrastructure that can be used to maintain a new solution,
  • it is a temporary solution that allows us to test Hadrone PPM without investing in infrastructure or engaging the IT team.

Are there any other models of using Hadrone PPM software?

Yes, we can distinguish two other possibilities:

  • purchasing a license of the Hadrone PPM software and installing it in the Customer's private or public cloud,
  • purchasing a license of the Hadrone PPM software and using the service of maintaining the software in Hadrone's cloud.

The final choice of the software usage model can also depend on other specific requirements and circumstances of the Customer. If you would like to find out which model of using Hadrone PPM software would be best for your organization, feel free to contact us – https://hadrone.com/pl/contact/. We're happy to assist!

Can I switch from SaaS to On-Premises or vice versa?

Yes, in Hadrone PPM, you can! This is an important feature to highlight, as not all PPM solutions offer this flexibility. Technically, this involves migrating the database, ensuring that no data is lost, and users will continue working as usual (only the web address of the application will change).

When might this happen? Sometimes, our Customers start using the Hadrone PPM software in the SaaS model due to the speed of deployment and no need for IT infrastructure or internal IT resources. After some time, however, it may become necessary to integrate Hadrone PPM with another IT system that cannot communicate with the cloud, thus making a transition to On-Premises model necessary.

The Customer may also need to move Hadrone PPM from their own IT infrastructure to our cloud, for example, as part of a broader migration program to public cloud solutions. This is also possible. This could involve:

  • purchasing a service to host the Customer's existing Hadrone PPM software in our cloud,
  • setting up new cloud access to Hadrone PPM after the current software license expires.

In both cases, there is no risk of losing project data and the migration happens within a few days.

Does the choice of the Hadrone PPM software usage model impact the deployment process?

It does, but only to a small extent.

The difference lies at the start – in the On-Premises model, the software is installed on the Customer's infrastructure, so IT resources and the Customer's team are involved. In the SaaS model, all the work is done on our side, and the Customer simply gains access to the functioning software.

The subsequent steps of the deployment, such as analysis, software configuration, training materials preparation, and user training, are the same for both models. The user experience is also the same – users just enter the correct address in their browser and start working.

The main differences may arise when it comes to integrations, both out-of-the-box (built into the Hadrone PPM software) and custom ones developed during the deployment. A good example is the integration with Active Directory – in the On-Premises model, we use a ready-made integration with MS Active Directory, while in the SaaS model, we use an integration with Entra ID (formerly Azure AD). However, these are technical details, as there is no difference for the user.

Post-deployment services also do not differ – for both models, we offer SLA service, email support for users and additional support billed on a Time & Material basis.