The Rootly Edge Connector lets you securely integrate internal services, monitoring tools, and automation workflows with Rootly—even if those systems live behind your firewall. By deploying the Edge Connector within your network, you can safely send alerts, trigger workflows, and interact with Rootly APIs without opening inbound access to your environment.
Why it matters
Many enterprise environments operate in restricted networks where exposing services to the internet is not allowed. Historically, this created friction when integrating internal monitoring or operational tools with external incident management platforms.
The Rootly Edge Connector solves this by establishing a secure outbound connection from your infrastructure to Rootly. This allows your teams to:
- Integrate internal monitoring systems that cannot be exposed publicly
- Trigger incidents, alerts, or workflows from private environments
- Maintain strict network security policies without compromising incident response automation
- Connect on-prem systems to Rootly with minimal operational overhead
How it works
- Deploy the Rootly Edge Connector inside your network or private infrastructure.
- The connector establishes a secure outbound connection to Rootly.
- Internal systems can then communicate with Rootly through the connector to send alerts, trigger workflows, or interact with APIs.
This architecture ensures that no inbound firewall rules or public endpoints are required, making it ideal for regulated or security-sensitive environments.
Getting started
- Deploy the Edge Connector within your internal network.
- Configure it with your Rootly credentials and environment settings.
- Connect your internal systems to the connector to start sending alerts or triggering Rootly workflows.
Check out the docs to learn more and get started.
With the Edge Connector, Rootly becomes easier to integrate into high-security and on-prem environments, enabling teams to automate incident response while keeping their infrastructure fully protected.
