Integration types

The first step to creating an integration with Acronis Cyber Platform is to identify what type of integration you need.
Read the type description, consider the examples, and identify which integration type you will build.
There are three types:

Inbound integrations (CyberApps)

Inbound integrations (CyberApps) fetch data from a cloud service to present and process on Acronis Cyber Platform.

Example

An ISV provides remote access functionality. Currently, potential customers must find the cloud service, perform due diligence, and evaluate the service before they even propose purchasing a license to senior management.
The ISV sales team has identified Acronis technology ecosystem partners as a major potential for growth. They have argued that providing the service with a familiar, Acronis-native UX from within the Acronis Cloud Platform will attract these new customers far more easily because Acronis partners can easily find the service, pay for it, and enable it with the assurance that Acronis has already tested and certified the integration.
The ISV marketing team wants to easily manage evolving marketing materials for the integration and deliver them effortlessly to the Acronis target market.
The ISV sales and finance team wants to manage Acronis integration customer information, and to access sales data and reports in real time.
The ISV product development team constantly improves service functionality and the interface, but the product manager find update deployments complicated and customer reaction to updates are sometimes painful.
The ISV wants to be able to effortlessly update functionality and interface, and for the product manager to be able to deploy updates worldwide or regionally.

Note

If you are going to build a CyberApp, see Inbound integrations (CyberApps).

Outbound integrations (API-based integrations)

Outbound integrations are API-based integrations, which allow Acronis partners and customers to provision, deploy, manage, and monitor Acronis services and data through the vendor cloud platform.

Example

An ISV provides Remote Monitoring and Management (RMM) functionality.
Their platform allows deployment, monitoring, and management of multiple services. They already work with other data protection companies, and some of their customers have requested that they also support Acronis. The ISV wants to connect to Acronis Cyber Platform, collect information from their customers’ Acronis environment - such as list of tenants, workloads, users, and workload-specific information such as workload status and protection plan - and present it on their platform. The ISV also wants to push particular tasks to Acronis agents for those customers.

Note

If you are going to build a outbound integration, see Outbound integrations.

Custom integrations

Custom integrations are built for very specific needs of an organization and/or its end customers. As such, they are only made available in a specific partner tenant.
They are built to simplify ISP operational activities and/or to integrate services into Acronis Cyber Platform. They can be inbound, outbound, or a combination of both.

Note

Custom integrations are not generally offered through the Acronis data center integration catalogs.

Example

An ISP wants to add a custom alert type that would be triggered under specific conditions and be shown in Acronis Cyber Platform.
They want to save their new custom alert type in their own partner tenant.
Once the alert is saved, they want to be able to reuse it in all their customer tenants.
The ISP also wants to provide one of their services to their customers via Acronis Cyber Platform and to configure and manage the service’s data through Acronis Cyber Platform.

Note

If you are going to build a custom integration, contact us by clicking the Contact us button on the Acronis Cyber Protect Cloud Solutions Portal.