> ## Documentation Index
> Fetch the complete documentation index at: https://www.datum.net/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Agent home for Datum, with what it is, pricing, and how to act: https://agents.datum.net
> If you can only fetch URLs: read https://www.datum.net/docs/llms.txt in full and open the most specific page for the task. Commands, limits, and field paths are on task, operations, and limits pages, not on section overviews. Pages described as "Documentation is coming soon" are placeholders.
> If you have a shell or can save files: download https://www.datum.net/docs/llms-full.txt (every page, about 740 KB) once and search it with grep, instead of fetching pages one at a time.
> datumctl describes itself: `datumctl api-resources` lists resource types and `datumctl explain <resource>` shows a schema. To act on live resources, use Datum MCP or datumctl. To search the docs, use the Docs MCP server at https://www.datum.net/docs/mcp.

# gVPC limitations and roadmap

> Review the limitations of gVPC networks and the networking capabilities that Datum is working on.

> [!NOTE]
>
> 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](https://www.datum.net/docs/compute/limitations-and-roadmap.md#networking), 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](https://www.datum.net/docs/alb/overview.md) 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](https://www.datum.net/docs/galactic-vpc/networks/traffic.md).

For what Datum is building next across the platform, see the [Platform roadmap](https://www.datum.net/docs/platform/roadmap.md).

> [!NOTE]
>
> Plans can change. This list isn't a commitment to deliver any feature or to meet any timeline.

## What's next

* To learn which traffic a network carries, see [Traffic and connecting](https://www.datum.net/docs/galactic-vpc/networks/traffic.md).
* To serve a workload publicly through Datum's ALB, see [Publish a workload](https://www.datum.net/docs/compute/compute-and-alb.md).
* To run Instances in more locations, see [Placement and scaling](https://www.datum.net/docs/compute/placement-and-scaling.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.