# osConnect Reference Designs

# Example Design 1

With this design, the customer leverages nearby osCloud POPs to quickly offload network traffic from internet providers to the osCloud network. In this scenario, the customer's Phoenix office connects to osCloud AZ01, which is about 5ms of network latency away. Once on the osCloud network, internet traffic is able to locally egress, secured by an osProtect Cloud Firewall, and customer-bound traffic is able to traverse the osCloud backbone (10 Gbps) and reach is final destination.

Las Vegas and Reno offices follow the same logic, except they prefer osCloud NV01 as their primary point of ingress, since it is also around 5ms of network latency away.

In this scenario, the customer's primary data center is colocated with osCloud, or in the same metro area. osConnect infrastructure is not required at the data center site, since a 10 Gbps metro cross connect is implemented. The customer also maintains osProtect firewalls in their data center to secure hosted traffic.

# Example Design 2

With this design, the customer prefers to keep the majority of their transit off the osCloud network, in favor of a more direct approach. With these requirements, we place the osConnect Aggregation servers onsite at the customer premises:

Internet-bound traffic backhauls to the customer data center via the secure osConnect network and is secured with osProtect firewalls.

Additionally, osCloud services can still be leveraged to provide cloud services. In this example, the customer still using osProtect cloud firewalls to provide a secure and highly available remote access VPN solution to their employees, while still providing connectivity to company IT resources.

# Example Design 3