Core formats
Open the Export menu (top right of the subnet table) to pick a format. Most formats also round-trip through the Import button next to it.
- JSON the canonical format. Holds the full subnet tree, every label / notes / VLAN / AZ, plus the parent network, mask, and provider. Re-import this file to restore the exact workspace. A separate all workspaces option bundles every open workspace into one JSON file.
- CSV flat table:
cidr, label, notes, vlan, az, hosts. Opens in any spreadsheet. - YAML same shape as JSON, human-readable.
- Markdown documentation paste. A rendered tree plus a per-subnet table.
- Print / PDF opens your browser's print dialog; pick "Save as PDF" there.
- SVG topology view as a vector image.
Infrastructure as Code Terraform
The Infrastructure as Code… entry opens a modal with two choices:
- Cloud AWS, Azure, GCP, Huawei Cloud, Alibaba Cloud, Oracle Cloud, IBM Cloud.
- Target one
resourceper subnet, or a single aggregate VPC resource that nests every subnet.
Output is Terraform HCL (.tf) only. CloudFormation, Pulumi, and Ansible exports
were removed Terraform is the one IaC format we commit to supporting across every provider, and users who
need other tooling can translate from the HCL output.
Re-exporting the same plan produces the same bytes, so CI diffs stay clean.
IPAM paste-import
The top-level Import button handles two IPAM formats as paste-in content. Format detection is automatic paste the text and the parser picks up columns versus keys.
- Infoblox CSV columns:
network, netmask, label, notes, vlan. The netmask column accepts either the dotted form255.255.255.0or a full CIDR like10.0.0.0/24. - NetBox YAML keys:
prefix,descriptionorname,commentsorcomment,vlan. The VLAN field accepts a plain number or a NetBox-style object (vlan: { id: 101, name: vl-dev }); the first number in the field is used.
There is no dedicated IPAM tool modal. One Import button covers JSON snapshots, all-workspaces bundles, Infoblox CSV, and NetBox YAML.
Share link
Press the Share button in the sidebar footer to copy a URL of the form
?state=…. The link encodes your entire workspace tree, labels, VLANs, provider and opening
it in any browser restores the exact plan. No sign-up, no server round-trip.
For multi-workspace fleets (like the Hybrid and Enterprise examples) the Load buttons use a short
?bundle_url=/examples/<fleet>.json form that fetches the bundle JSON at runtime, so the
URLs stay under the browser's length limit regardless of fleet size.