Independent Software Vendors

We partner with Independent Software Vendors (ISVs)

InCountry approach

  • Work with the ISV to determine best path for integrating the InCountry Data Residency-as-a-Service (DRaaS) platform with their SaaS application(s) so that customers can meet regulatory requirements with minimum pain.
  • Engage the ISV’s customer facing teams to determine the customer use-cases that need to be addressed to help the ISV close more deals and/or stem attrition.
  • Support ISV referred customers by helping them determine the most appropriate data residency model that can be used with the ISV’s application(s).
  • Support ISV’s customer facing teams by participating on customer calls to explain the various data residency models that can be used to address the customer needs.
  • Help ISV support customers who need or prefer to operate on sovereign cloud infrastructure.

ISVs problem

ISVs have developed SaaS-based applications that run on the infrastructure of one or two cloud providers. Customers are regulated entities that need to meet data residency requirements laid out in the data protection regulations of the countries in which they operate.  Frequently, there is little overlap between the more highly regulated jurisdictions in which customers operate and the locations where the ISV infrastructure resides.  Existing customers are at risk of churning if the ISV cannot help them meet their compliance obligations.

Independent Software Vendor partners

Salesforce
Servicenow
Cegid
Veeva

Why become an InCountry ISV?

InCountry ISVs partner benefits

Aspect
Do it Yourself
Partnering with InCountry
Cost
Maintenance & Operations
Connectivity
Flexibility
Time-to-value
Opportunity cost
High
i CapEx required to build DC’s, infrastructure and develop app integration
High
i Maintain infrastructure, SOC, risk monitoring and adhere to an audit and compliance regiment
Low
i Typically single use case
Low
i Build new DC’s when data protection regulations change
Months/years per country
High
i Not core business
Low
i OpEx for resources needed to perform application integration with the InCountry DRaaS
Low
i Managed by InCountry
High
i Access InCountry’s network of PoPs
High
i Support of various data residency models, adapt quickly to regulatory changes
Weeks total
i Once integration is complete, all InCountry PoPs globally are accessible
Low