Skip to main content

Introduction to Full Self-Hosted Deployment

Frends Agents

Ossi Galkin avatar
Written by Ossi Galkin
Updated over a year ago

Full Self-Hosted deployment

If you have only Cloud or Ground Agents in Frends, you are having a full Self-Hosted deployment. Not having any PaaS Agents gives you full control of your integrations. This will also give full responsibility of your integrations, since you need to operate all your Agents in addition to integration development.

The prerequisites for having a full Self-Hosted deployment are the same as in Multicloud and Hybrid deployment. If you want to have Cloud Agents, then you need to have a cloud service provider in use and you need to have sufficient permissions to deploy resources to the cloud service provider. If you want to have Ground Agents, then you need to have physical machines in which you can install the Frends Agent Service and you need to have sufficient permissions on the machine to do the installation. In both cases you also need to have admin permissions in Frends to create new Agents and Agent Groups.

If you have PaaS Agents, then those need to be in different Agent Groups from the Cloud or Ground Agents. However, there are no restrictions of having Cloud and Ground Agents in the same Agent Group, since those are both Self-Hosted Agents from the Frends point-of-view. Hence, you can mix and match Cloud and Ground Agents in different Agent Groups as you see fit.

A business use case for having a full Self-Hosted deployment is that you want to have full control over Agents running your integrations in addition to integration development. In some cases, this is required, for example the processing of sensitive data has restrictions over how you can process the data and where it is processed. In addition, if your integrations require specific tools to execute successfully, then you need Self-Hosted Agents since you can install your tools there.

The next article is Introduction to Scaling

Did this answer your question?