Network & CDN integrations
Maps network topology, DNS records, and edge configurations. Pushes firewall rules, DNS updates, and CDN purges through automated workflows.
Changes that ship with an approval gate
Configuration templates, firewall rules and DNS records are pushed through the same approval path as any other change, and the record stays on the ticket.
Taking capacity in and out of rotation
Nodes and pool members are enabled or disabled from an incident, so maintenance and incident response do not need a separate console.
Addressing and records kept straight
DNS host records and IP allocation are handled as part of provisioning, so the network picture matches what is actually deployed.
Network & CDN tools we connect to
Common questions
Is this a replacement for our network management tools?
No. It connects to them. They stay the place configuration lives; STLabs is how changes are requested, approved and recorded.
Can changes be made automatically during an incident?
Only if you permit it. Network actions can be restricted to approval-only while other categories run automatically.
Does it work across multiple vendors?
Yes. Devices from different vendors appear in one topology, which is the point of reading them into a shared graph.