A new architecture called BYOC

[rakhirhif8963]

BYOC: How to Provide Secure Access for Providers to Customer Networks
12.03.2024
As the need to manage data privacy, sovereignty, location, and cost grows, more enterprise use cases for the Bring Your Own Cloud (BYOC) model will emerge, writes Chad Tindall, CTO and vice president of solutions architecture at ngrok, on Network Computing.

To be successful, many SaaS solutions need access to their customers’ data. For example, Databricks, which is used by more than half of the Fortune 500 companies to process, analyze, and monetize massive amounts of data, needs to connect to its customers’ cloud accounts to process and store data, ensuring security and scale.

However, sending data to suppliers for processing is fraught with various challenges. The rapid growth in data volume and complexity makes this approach impractical, often requiring significant processing and transmission costs when moving data out of the customer’s cloud and/or into the supplier’s cloud. And perhaps most importantly, handing cayman islands mobile database control raises concerns about privacy, sovereignty, and data security.

Meet BYOC
can be used to address these issues. It involves deploying the data plane portion of a SaaS provider’s software stack to a customer’s environment to store, process, and analyze their data. The control plane consists of all the backend services and compute resources needed to configure and manage data sets in the provider’s network and runs in the SaaS provider’s cloud environment, connecting via API to the BYOC data plane running on the customer’s network. BYOC software addresses privacy, sovereignty, and cost concerns, but SaaS providers face many challenges in connecting to it on customer networks.

Issues with accessing BYOC on a customer's network
Gaining network access to the data plane deployed in a customer’s environment can be a complex and time-consuming process. Providers often face VPN, VPC peering, PrivateLink, and firewall configurations that require extensive review and approval from multiple stakeholders, including the customer’s NetOps and SecOps teams. Each customer’s environment is unique and requires custom network configurations, which prevents rapid scaling across accounts. This means that end users cannot quickly gain the desired benefit, leading to poor adoption, general dissatisfaction early in the journey, and even customer churn.