What is a Containerized CSG?

A Containerized CSG (cCSG) is a containerized software form factor of the Cloud Services Gateway that customers deploy on their own cloud server, rather than on Versa hardware or a Versa-provisioned VM. Offered in sizes L, M, XL, and 2XL, it runs VOS to deliver SD-WAN branch or SASE gateway functionality inside the customer’s cloud environment.

Key takeaways

• cCSG is a containerized CSG customers run on their own cloud server.
• Offered in four sizes: cCSG-L, cCSG-M, cCSG-XL, and cCSG-2XL.
• Requires VOS 20.2.x or later installed on the customer’s cloud server.
• High availability configuration requires the cCSG-2XL SKU.
• Ordered and provisioned through the Versa Titan portal.

On this page: Why it matters · How it works · cCSG sizes · Containerized CSG & the VersaONE platform · FAQ

Why is a Containerized CSG important?

Not every customer wants – or is able – to rack physical hardware or hand a full virtual machine over to a vendor-managed appliance. Some already run workloads on their own cloud infrastructure and want SD-WAN or SASE gateway functionality to live there, under their own compute account, alongside everything else they operate in that environment. The Containerized CSG exists for exactly that case: a lighter-weight, container-based way to run CSG functionality on infrastructure the customer already owns and controls.

It also matters for how Versa’s MSP and reseller channel sells and provisions gateway capacity. Because a cCSG is ordered as a device SKU through the Versa Titan portal – the same ordering and fulfillment surface used for physical CSG hardware and vCSG virtual appliances – operators, MSPs, and resellers can offer customers a cloud-native deployment option without a separate sales or provisioning process.

What is a Containerized CSG?

A cCSG is a containerized instance of VOS that a customer deploys on their own cloud server, selected as one of the hardware device options – alongside CSG and vCSG – when adding a device through the Versa Titan portal. Because the container runs on customer-owned cloud infrastructure rather than Versa-supplied hardware or a Versa-managed VM, deployment carries prerequisites the customer must complete before the device can come online: create a cloud server and mount it to an internal gateway so it can reach the internet, install VOS Release 20.2.x or later on that cloud server (matching the version running on the Versa Director node), and collect the cloud server’s LAN subnet information so the cCSG’s LAN interfaces can be configured to match the cloud environment’s networks before deployment.

Once those prerequisites are met, the cCSG is added and activated through Titan like any other gateway device, with a device SKU, software license tier, and subscription duration selected at order time.

cCSG sizes

The cCSG line is sized by device SKU: cCSG-L, cCSG-M, cCSG-XL, and cCSG-2XL, mirroring the sizing convention used for the Virtual CSG line. Sizing determines capacity for the gateway role the container will perform. Not every gateway type is available on every size – private, multitenant, and multitenant RAC/RAS gateway configurations are not available on the cCSG-M model, so sites needing those services require a larger SKU. High availability is a 2XL-only capability: configuring and deploying HA on a cCSG requires selecting the cCSG-2XL device add-on. License tiers (Enterprise Security, Advanced Security, and, on eligible SKUs, Secure Application Optimization) and subscription durations of one, three, or five years are selected independently of size at order time.

Containerized CSG & the VersaONE platform

A cCSG is ordered and provisioned through the Versa Titan portal – the MSP- and reseller-facing order-management and device-activation surface for Versa’s gateway hardware and software SKUs – but once deployed it participates in the platform the same way any VOS device does. It can be configured as a SASE gateway, enabling services such as Secure Web Gateway (SWG) and Versa Secure Access (VSA) when set up as a private gateway, or serve an SD-WAN branch role, connecting to the fabric like a physical or virtual CSG. The container form factor changes where the software runs – the customer’s own cloud server instead of Versa hardware or a Versa-managed VM – not what the software does once it’s onboarded.

Frequently asked questions

What is the difference between a cCSG and a vCSG?

A cCSG is a containerized instance a customer deploys on their own cloud server; a vCSG is a virtual-machine form factor deployable on a hypervisor or in a public cloud VPC. Both share the same L/M/XL/2XL sizing convention and serve SD-WAN branch or SASE gateway roles.

What do I need before deploying a cCSG?

A cloud server mounted to an internal gateway for internet reachability, VOS Release 20.2.x or later installed on that server (matching the Versa Director version), and the server’s LAN subnet information collected so the cCSG’s LAN interfaces can be configured to match the cloud network.

Which cCSG size do I need for high availability?

cCSG-2XL. High availability configuration on a Containerized CSG requires selecting the 2XL device SKU or add-on; smaller sizes do not support HA deployment.

Are all gateway types available on every cCSG size?

No. Private gateway, multitenant, and multitenant RAC/RAS gateway configurations are not available on the cCSG-M model. Sites that need those gateway types require a larger cCSG SKU.

How is a cCSG ordered and managed?

Through the Versa Titan portal: select cCSG as the hardware device, choose a device SKU, software license tier, and subscription duration. Once deployed on the customer’s cloud server, it’s managed like any other VOS gateway device.

More on Versa

If you want to learn more, these are sources we trust.

Related terms

If you’re reading about the Containerized CSG, these are worth looking at next.