On-premise Deployment
On-premise deployment
There are various reasons for businesses to choose an On-premise deployment model - data sensitivity, regulatory compliance, cost considerations, etc. Thus, to meet its customers’ requirements and ensure best-in-class security measures GitProtect.io allows deployment of the backup agent within the organization’s own environment - both physical data center and its preferred cloud service like Azure or AWS.
In this case, the organization installs the GitProtect.io backup agent on a machine of its provision which means that the backup software works locally in the organization’s ecosystem. Thus, data never leaves the customer’s own infrastructure.
Backup target
Note that the storage location of the copies remains independent of the location of the management server. Thus, even if the organization uses a data residency of its choice, it still has the option to store its DevOps data locally, and vice versa - with an On-Premise service, GitProtect.io’s users can choose to store data in the cloud.
Whichever deployment model the organization chooses, with GitProtect.io it gets best-in-class security and access management measures - AES encryption in-fight and at-rest, the possibility to customize the encryption key and set different backup roles and permissions, ransomware protection, and Disaster Recovery Technology. Thanks to GitProtect.io’s multi-storage compatibility, it’s easy to assign various backup storage destinations, fulfilling the 3-2-1 backup rule - when an organization has at least 3 copies in no less than 2 storages, one of which is offsite. Thus, organizations can easily meet the Shared Responsibility Model and keep up with security, legal, and compliance requirements.