Recursyv builds cloud hosted integrations. Built on a message bus paradigm our approach to integrations provides a truly reliable, scalable and flexible solution for synchronising data between apps and platforms. We provide all of the infrastructure from the server to the monitoring tools, meaning you do not have to provision any additional technology to connect your systems. As we build integrations to only pass encrypted information, not store it, security is ensured as is compliance with most info-sec policies.
The message bus architecture and data polling approach provide a basis for ensuring data resiliency. The architecture is designed to ensure data delivery is successful even if failures occur either retrieving or sending data at the first try.
Connectivity and data integrity issues are handled in an appropriate and resilient manner to deliver information reliably and accurately to the destination. This prevents having to manually copy across missed data if there are connectivity issues with a system.
Our proactive monitoring informs us if there are issues with the service 24/7/365. Our engineers are immediately notified of any errors and these are quickly analysed.
Where issues will result in operational interruptions to syncing data, Recursyv will inform you about the interruption as well as what we are doing to minimise impact and restore service.
In some cases we are even able to advise you about potential data or connectivity problems within your application before you know about them.
Recursyv integrations are deployed within Microsoft’s Azure cloud. Azure meets a broad range of international and industry-specific compliance standards, such as ISO 27001, HIPAA, FedRAMP, SOC 1 and SOC 2, as well as country-specific standards, such as Australia IRAP, UK G-Cloud and Singapore MTCS.
Recursyv does not retain data beyond the time when it is in transit. Data in transit is encrypted using a 256-bit encryption algorithm, with the encryption keys being unique to each integration tenant.
Configuration data is stored behind firewalls ensuring only a restricted set of IP addresses can access it. Configuration data is also encrypted using an industry standard 256-bit encryption algorithm and a different encryption key set to those used for data in transit.
Recursyv is deployed in a number of geographies across the world, from the Americas to Australia. The service can be configured on a customer by customer basis to constrain all data to a particular geography (in order to meet regulatory requirements for example) or to allow cross geography processing to provide a greater level of redundancy.
Applications and their data change and evolve over time, and the services around them need to do the same. Recursyv is designed to achieve data transformations and mappings using no-code configuration – meaning they can be changed quickly and easily as your application estate changes.
The message bus architecture also allows for a natural disconnect between applications, allowing them to change relatively independently of one another. This prevents you needing to commission large change projects to resolve complex data dependency problems between platforms.
Recursyv uses dynamic connectors to talk to platform APIs. If we have already built a connector, this will be used as-is, or modified for greater speed of delivery. If it is a new system we can create it from scratch in order to meet almost any requirement or to connect to any end point.
Our integrations are built on a foundation designed to support common SaaS API protocols, including RESTful, SOAP, RDMS and ODMS which means that creating a connector is a quick process. Data formats are interchangeable (between JSON, XML etc.) allowing us to easily sync data between different platform stacks and environments.
Custom connectors can be written quickly to either connect to bespoke applications or to perform very specific operations or processes as required.
Foundation connectors have been built for common protocols, allowing us to quickly connect thousands of well-known applications. When we build new application connectors, this is where we start.
RESTful
SOAP
SMTP