Skip to main content
gVPC is in preview, and the networking.datumapis.com/v1alpha API can change.

Limitations

In addition to the networking limitations that apply to all of Compute, networks have the following limitations:
  • Each workload attaches to exactly one network through one network interface, and it can’t move to another network.
  • Instance addresses aren’t reachable from the internet. To serve traffic publicly, attach an ALB to the workload.
  • The networkPolicy field of a network interface has no effect. Don’t rely on it to restrict traffic. Firewall rules are a planned capability.
  • You can’t choose a network’s address ranges or create your own subnets.
  • Networks carry Compute traffic only in the locations where Compute runs: us-central-1, us-east-1, and us-west-1.

Planned capabilities

Datum is working on the following networking capabilities:
  • Firewall rules: Security groups that control the traffic to and from your Instances.
  • Private DNS: Private DNS names, so Instances can find each other without IP addresses.
Outbound internet access, including IPv4 destinations, and viewing networks in the Datum Cloud portal are already available. For details, see Traffic and connecting. For what Datum is building next across the platform, see the Platform roadmap.
Plans can change. This list isn’t a commitment to deliver any feature or to meet any timeline.

What’s next

Last modified on October 23, 2026