Private networks
Execute autonomous workflows inside your security boundary. Connect Plannix Bot sandboxes directly to non-routable internal subnets without opening inbound firewall ports.
Private network architecture
Plannix provides dedicated network interfaces (ENIs) attached directly to your dedicated peering subnets. All communication between the bot runtime and your internal resources travels across encrypted cloud provider backbones.
Zero Inbound Exposure
No public IP addresses are assigned to private worker nodes. Traffic originates outbound via your established gateways.
Microsegmentation
Restrict bot access to precise CIDR blocks and ports using cloud security groups and network ACLs.
AWS Transit Gateway & VPC Peering
Connect your AWS environment to your dedicated Plannix tenant via AWS Transit Gateway (TGW) or direct VPC peering:
# Accept peering attachment in your AWS account
aws ec2 accept-transit-gateway-peering-attachment \
--transit-gateway-attachment-id tgw-attach-0123456789abcdef0 \
--region us-east-1Azure VNet Peering & ExpressRoute
For Microsoft Azure environments, establish non-transitive VNet peering with low-latency routing inside the same Azure geography.
GCP VPC Peering & Cloud Interconnect
Configure Google Cloud VPC Network Peering to access private GKE clusters and Cloud SQL databases using internal RFC 1918 addresses.
Internal private DNS resolution
Forward custom DNS domains (e.g. *.corp.internal) to your private DNS servers under Organization Settings > Networking > DNS Forwarding.