Networking

StrataGateway networking is being designed around simple connectivity, predictable behavior, region-aware infrastructure, secure defaults, developer-controlled firewall policies, and future global expansion.

Compute instances may receive public IP connectivity where available. Planned capabilities include public IPv4, public IPv6, outbound internet access, inbound traffic controlled through firewall policies, and future public DNS integration.

Private networks allow workloads inside the same region or project environment to communicate without exposing internal traffic directly to the public internet.

StrataGateway is being designed with dual-stack networking in mind. IPv4 is intended for compatibility with existing internet infrastructure, while IPv6 is intended to provide native next-generation addressing where supported.

Networking is region-aware. Resources inside the same region are expected to use low-latency regional networking, and future infrastructure phases may introduce private inter-region connectivity.

Global routing design and inter-region connectivity remain part of the StrataGateway infrastructure roadmap.

Instance networking will be controlled through firewall policies that can define inbound and outbound rules, protocol selection, port ranges, source and destination CIDR rules, and reusable policies.

Planned network events include IP allocation, attach, update, detach, and release. Exact timing and guarantees are not defined yet.

This restrained topology shows the intended flow between the internet, public entry points, firewall policy, and region-local private services.

The API surface below is illustrative and may change before public release. Use it to understand the planned request shape rather than a live contract.

curl -X POST "https://api.stratagateway.com/v1/networks" \
  -H "Authorization: Bearer $STRATA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "production-private",
    "region": "fra-1",
    "cidr": "10.10.0.0/24"
  }'

{
  "id": "net_52a8f1",
  "name": "production-private",
  "region": "fra-1",
  "cidr": "10.10.0.0/24",
  "status": "provisioning"
}

Illustrative API preview. Production endpoints, payloads, network identifiers, and response formats may change before public release.

Networking design should assume a least-privilege posture from the start. Use SSH keys instead of passwords, restrict administrative ports, prefer private networks for internal services, and review firewall rules before production deployment.