Skip to main content
All nodepick compute nodes are provisioned on an isolated Virtual Private Cloud (VPC) network by default. Each node receives a private IPv4 address on the VPC subnet and is protected from direct public internet exposure.

Virtual Private Cloud (VPC)

A VPC provides an isolated private network for your compute nodes. Nodes deployed into the same VPC can communicate privately over low-latency internal networking.

Managing VPC Networks

Create a new VPC network:
List all active VPC networks:
Inspect details of a specific VPC:
Delete a VPC network (must have no active nodes):

Deploying Nodes to a VPC

Attach nodes to a specific VPC using the --vpc flag in the CLI or the vpc parameter in the SDK:

Public IP Addresses

Public IPv4 and IPv6 addresses are dynamic add-ons assigned post-provisioning. When you need direct public ingress or external service exposure, attach a public IP address.

Attaching a Public IP

The CLI and SDK automatically detect whether an address is IPv4 or IPv6:
Attach an auto-allocated public IPv4:
Attach an auto-allocated public IPv6 prefix:
Attach a specific reserved IP:

Detaching a Public IP

When public internet access is no longer required, detach the public IP. The node remains running on its private VPC address: