Segal VPC
Separate private service traffic from public access through project-scoped networks and subnets.
Engineering-led activation. Production access depends on an authorized provider account, a customer-specific service binding and confirmed availability.
How the service fits.
Project-scoped private networks and subnets. Connectivity is subject to regional service support.
- 1
Define the regional network and address ranges
- 2
Attach instances and supported managed services
- 3
Add only the required routing and public ingress
Service architecture
- Address ranges and routing are recorded as infrastructure configuration
- Private connectivity is separate from application authorization
- Firewall policy follows the workload’s trust boundaries
Operating boundaries
- Overlapping address ranges complicate peering and migration
- A private network alone does not encrypt every connection
- Connectivity and supported service integration vary by region
Deployment & support
Segal provides the branded service experience and coordinates configuration, support and commercial scope. The infrastructure service is supplied through OVHcloud; provider eligibility and applicable service terms must be confirmed before activation.
Upstream service: Private Networks. Provider specifications were reviewed on 24 October 2026; actual inventory and quota are checked separately.
Upstream technical reference