On-premise integrations

Blendr.io uses the public API's of cloud platforms to exchange data. These API's can be SOAP, REST, GraphQL, JSON-RPC or any other type of API, typically running over HTTPS or websockets. Further more, Blendr.io can exchange files over FTP, SFTP, FTPS, and a wide range of cloud storage providers such as Dropbox, Google Drive, Google Cloud Storage, Azure, AWS S3 and others.

For integrations with so called on prem installations, Blendr.io offers a few different strategies.

API over VPN

If the on prem software has an API, the API can be made available for access by Blendr.io using a VPN or by opening up a port on the firewall. IP's can be whitelisted to limit access.

Push from on-prem to Blendr.io

The on prem software can make API calls to Blendr.io, e.g. by posting data to an HTTPS endpoint of a triggered Blend. This way the data exchange is initiated by the on prem software, which pushes data to a Blend on Blendr.io. This way the Blend can accept data, but it can also send data back in the response, which can be consumed by the on premise software.

If the on prem software supports for example webhooks, or the ability to add a custom script to make HTTPS calls, this scenario can be applied.

The triggered Blend can then integrate with other cloud applications, which means that it acts as a proxy between the on prem software and other platforms. alt text

File exchange using (S)FTP or cloud storage

The on prem software can export data to an (S)FTP server on a regular basis, e.g. daily, and a scheduled Blend in Blendr.io can consume these files by connecting to the same (S)FTP server. The files can be in CSV, they can contain XML or any other data format.

Similarly the on prem software can import data from (S)FTP files, where the files are created by a Blend on Blendr.io.

Same as before, the Blend acts as a proxy, it exchanges data with the on prem software using files, and it can then push data to other cloud applications using the regular Blendr.io connectors.

3rd party agents

For certain on prem software, third party commercial agents are available that run locally, communicate with the on prem software, and then communicate with a REST API online. Such agents can communicate with a Blend, since each Blend acts as a REST API (it has an HTTPS endpoint).

More info:

Custom agent development

If none of the above scenario's are applicable, a custom agent can be developed that runs on prem on a local server. The agent communicates with the on prem software, e.g. using CLI (command line interface) or direct database access. The agent can make API calls to Blendr.io to exchange data in 2 directions. Blendr.io has a network of certified partners that can help with custom agent development.