Daniel, Cyclr’s Head of Marketing sat down with Cyclr’s CEO Fraser Davidson and chatted about integration. Specifically about enterprise integration, data processing and compliance and how they play a crucial role in the consideration process.
How soon into the process of engaging with clients does data hosting and processing get focused on with an Enterprise client?
If you’re dealing with a young company it is more than likely you’ll be talking to a single decision-maker. They cover all elements of the buying process.
When you deal with a large enterprise, your first contact might not that have the decision-making capability. Due to them being in an exploratory phase. However, very quickly, other elements of the business will get involved. Especially in the proof of concept and other technical conversations regarding data. For instance, where the data is being processed, and how the infrastructure is deployed. This will quickly become a key purchasing and buying criterion.
When it comes to private deployments and managing their infrastructure suite, what kind of benefits does that bring to their DevOps/infrastructure teams?
Ultimately, it comes down to corporate preference. For instance, if they choose the self-hosted, self-management route they would prefer to have control of the DevOps environment. As well as control the infrastructure to keep data processing under their umbrella. This is rather than a subprocessor like an integration provider.
On the other hand, they could prefer managed service options. This is whereby it’s private cloud, single tenancy, scalable infrastructure, but handled within an integration provider. For example, Cyclr is a subprocessor with SOC 2 Type II compliance. We achieve managed service options on our shared instances all the time. Many benefits come with that, for instance, we do the infrastructure monitoring and management.
Both options provide strong benefits but it ultimately comes down to management and corporate preference.
What options are there for maintaining existing company-wide compliance levels?
When an enterprise is looking for an embedded iPaaS at a minimum the embedded iPaaS should have SOC2 Type II level compliance accreditation.
As an embedded iPaaS vendor, we are blissfully unaware of the many types of data flowing through your application environment. Therefore, this means that we need to treat every single piece of data and information as if it is personally identifiable information. As a result, we have high data security measures in place.
We are hosting a range of webinars discussing embedded iPaaS, integration building and more.
Check out the full list on our dedicated page.
