Network and Security Automation
The operating layer of the Cloud Gateway platform, running governed deployment workflows, runbook automation, infrastructure-as-code, and APIs.
Change at scale, run as a service
Automate is a key operating layer of the Cloud Gateway platform. It’s the part of the architecture that handles deployment, change and operational workflow, so the platform stays current without manual effort and changes happen at a pace that matches the business.
Most managed services keep change at arm’s length. Each change is a ticket, each ticket goes to a queue, each queue runs to a schedule. Even routine work takes weeks. Standardisation is patchy. Evidence of what changed and why is assembled after the fact, if at all.
Automate replaces that model. Standard work runs through governed workflows that are codified once and applied consistently. Templates drive provisioning of new services. Runbooks automate routine operational tasks. Every change is validated as it happens, captured as evidence, and surfaced in Observe in real time.
How automation is handled
Automate sits across the platform. Every capability in your tenant is provisioned, changed and operated through the same governed flow. This is the layer that determines whether a platform can actually keep pace with the business. Most can’t, because their automation stops at provisioning. Cloud Gateway extends it across change, evidence and operations.
Standardised templates
Service deployments follow patterns. New connections, new policies, new sites and new users come online against templates that meet your security and compliance baseline by default. Standardisation is the precondition for safe automation, not the enemy of flexibility.
Governed change workflows
Every change to the platform goes through a validated workflow. Approvals are captured. The change is checked against policy before it lands. The audit trail is generated as it happens. No ticket, no queue, no manual reconciliation after the fact.
Runbook automation
Routine tasks are codified and run by the platform. Common changes, response actions and operational checks happen on a schedule or in response to defined triggers, with human oversight where it matters.
Open APIs
Automate is accessible programmatically. We allow your ITSM, SIEM and reporting tools to trigger changes, raise tickets, and pull data through the same APIs we use ourselves (Beta).
AI-assisted operations
We’re building AI assistance into the operating layer for routine analysis, anomaly identification and operational triage. The platform will learn from trends and patterns to incrementally improve its effectiveness.
Managed, co-managed, or both
Automate doesn’t replace your team. It changes what your team has to do.
For a fully managed deployment, the platform is operated by Cloud Gateway, and Automate is the layer your team interacts with when they need to see, change, or report on the service.
For a co-managed deployment, the same automation is available to your engineers through role-based access in the Cloud Gateway portal. Your team handles the changes they want to own. We do the rest.
Beyond automation
are the services Automate operates. Every change to a connection, a policy, or a service is handled through the same governed workflow.
is where the automation surfaces. Changes appear in real time, validated and captured as they happen will full transparency.
is what the automation produces. Audit-ready evidence of every change, generated as a by-product the platform, not assembled after the fact.
Common questions
about Automate
What is network automation?
Network automation is the use of software and workflows to provision, change, monitor and operate network infrastructure without manual configuration. Modern network automation typically includes infrastructure-as-code templates, governed change workflows with approvals built in, runbook automation for routine operational tasks, and API integration with ITSM and orchestration tools. Cloud Gateway’s Automate layer delivers all of these as part of the managed service.
Can I trigger changes through my own ITSM or orchestration tools?
Coming soon! The Cloud Gateway platform will expose open APIs that allow customer ITSM, SIEM and orchestration tools to trigger changes, raise tickets, pull telemetry and integrate the platform into existing workflows. The same APIs Cloud Gateway uses internally will be available to customers, so the platform fits into the operating model the customer already runs.
What's the difference between managed and co-managed?
A managed deployment means Cloud Gateway operates every capability the customer takes, end to end. A co-managed deployment means the customer’s engineers take role-based access to the platform through the Cloud Gateway portal and operate the changes they want to own, with Cloud Gateway handling the rest. The same automation, change workflows and evidence generation apply in both cases. Co-managed is common for customers with strong internal capability who want operational reach into the platform without taking on full operations.
Connect. Protect. Observe. Assure. Automate.
Get your regulated connectivity right first time.