What is PagerDuty Runbook Automation?
PagerDuty Runbook Automation is an operational runbook automation platform for infrastructure, DevOps and SRE teams, built by PagerDuty, Inc., which converts manual procedures documented in a wiki or spreadsheet into standardized, auditable jobs. Each job encapsulates an ordered sequence of steps and can be triggered the web, the CLI, the API, a schedule, or inside an incident. Execution reaches servers on closed networks through runners installed in the customer's environment, which open an outbound connection instead of requiring an exposed inbound port.
The product grew out of Rundeck, acquired by PagerDuty in October 2020, and is the technical foundation of automation in the Operations Cloud. In practice it replaces the loose script on a specialist's laptop and the ten-step procedure pasted into a document — the situation where only one person knows how to restart the service and every night-time incident escalates to them.
Key PagerDuty Runbook Automation features
The product brings authoring, execution, scheduling and automation governance together.
- Workflow Execution — orchestrates complex step sequences with dependencies and conditions, instead of hand-chained scripts.
- Jobs with self-service delegation — publishes the procedure as a button for generalists, without granting shell access to the server.
- Key Storage with Key and Password Encryption — keeps passwords, API keys and tokens encrypted at rest and injects them into the job at runtime.
- Certified Enterprise plugins — ServiceNow, Kubernetes, Ansible, Datadog, VMware, GitHub, AWS SNS and SQL Runner, plus the Community Plugins catalog.
- Job Independent Scheduling and Blackout Calendaring — schedule each job on its own terms and block execution during defined critical windows.
- Access Control Rules Builder and Evaluator — build ACL rules in a graphical interface and test who can run what before publishing.
- Node Health Checks, Retry Failed Nodes and Failed Job Resume — verify nodes before execution and resume the job the last successful step.
- Job Activity Log and Workflow Visualization — record start, duration, status and output of every run and draw the flow for diagnosis.
PagerDuty Runbook Automation benefits
The first benefit cuts escalation, because a job published as a self-service action lets the first-line on-call engineer run the correct procedure without paging the specialist. The second reduces human error: the job always runs the same sequence, with Key Storage credentials, instead of relying on someone typing commands under pressure at three in the morning.
The third delivers audit traceability, because the Job Activity Log records who ran what, when, on which nodes and with what output. The fourth removes credential exposure, since the secret stays encrypted in Key Storage and is injected into the job without being revealed to the operator.
Who PagerDuty Runbook Automation is for
PagerDuty Runbook Automation is for teams with repetitive operational procedures concentrated in few people: infrastructure, DevOps, SRE, NOC, platform engineering and security teams that need to delegate execution without opening privileged access.
Three concrete scenarios: a bank that must prove in an audit who ran each production routine and relies on the Job Activity Log; a platform team that publishes a Kubernetes pod restart as a button for the service desk; an operation with servers on a closed network running automation through a runner without opening an inbound firewall port.
What sets PagerDuty Runbook Automation apart
The first differentiator is delegation without privilege: the job becomes a button-press action with its own ACL, which lets you hand execution to a generalist without handing over credentials or server access.
The second is closed-network reach, because the runner only needs outbound access to api.pagerduty.com and requires no exposed inbound port. The third is the tie to the incident lifecycle: through Automation Actions, the same job fires the incident, the mobile app, Slack, an Incident Workflow or an Event Orchestration rule, with alert context variables in PD-CEF format. The fourth is execution resilience, with High Availability Clusters, Auto Takeover, Job Queuing and Load Balanced Workloads.
System requirements
In the SaaS edition there is no server to install: PagerDuty hosts the platform and takes on patching, protection, monitoring and compliance, with a 99.9% availability SLA. Access is by browser, CLI or API.
To run automation in your own environment you must install a runner: Java 11 or higher, with Linux recommended (Ubuntu 18 or higher). The runner needs outbound access to api.pagerduty.com and, if it sits on a different machine the Self-Hosted instance, inbound access on port 80. A runner idle for five minutes switches to offline, and actions triggered in that window queue until it returns. The Self-Hosted edition installs on-premise or in a private cloud, and the Automation Actions connector also integrates Rundeck OSS version 4.0.
Editions and modules
There are two editions. Runbook Automation is the fully managed SaaS PagerDuty, with Enterprise Support, vendor-managed high availability and integrated SSO. Runbook Automation Self-Hosted delivers the same platform for on-premise or private cloud installation, with self-managed hosting, your own High Availability Clusters and integration with LDAP, Active Directory or SAML.
Automation Actions is the connector that exposes jobs inside the Operations Cloud, available to accounts that already have Runbook Automation in either edition, and it requires the PD Automation Actions user license. Related add-ons: Automated Diagnostics, a prebuilt library of diagnostic jobs, and PagerDuty Advance for Automation Digest, which summarizes job output, available in the United States and European Union service regions.
How much does PagerDuty Runbook Automation cost?
PagerDuty Runbook Automation is licensed per named user, with a platform fee added to the user count in the SaaS edition. The Self-Hosted edition is sized on request. The model is annual (subscription), with a multi-year option, and using the Automation Actions connector consumes the specific PD Automation Actions license.
There is no single list figure because the investment depends on sizing: number of users, edition chosen between SaaS and Self-Hosted, need for PD Automation Actions licenses, number of runners and environments covered, contract term, and whether it is a new purchase or a renewal. Two contractual points matter: under PagerDuty's official terms every person added to the account is a paid user, and the Self-Hosted edition does not auto-renew, which requires tracking the expiry date. To buy PagerDuty Runbook Automation in Brazil, OSB Software maps that scope with you, sends the commercial proposal, issues the Brazilian invoice and delivers the licenses — request a quote to get the exact figure for your scenario.
Frequently asked questions
Does PagerDuty Runbook Automation run on servers behind a firewall? Yes. The runner installed in your environment opens an outbound connection to api.pagerduty.com, with no internet-facing inbound port required.
Do I need PagerDuty Incident Management to use Runbook Automation? To author and run jobs, no. To trigger those jobs inside an incident through Automation Actions, yes — the connector requires a PagerDuty account with the PD Automation Actions license.
What are the runner requirements? Java 11 or higher, with Linux recommended (Ubuntu 18 or higher). The runner goes offline after five minutes of inactivity and pending actions run once it is back.
Does it work with open source Rundeck? Yes for the connector: Automation Actions integrates Rundeck OSS version 4.0, although capabilities such as Enterprise Support, high availability and certified plugins belong to the commercial editions.
Why buy PagerDuty Runbook Automation OSB Software?
OSB Software is an official PagerDuty partner in Brazil and supplies 100% genuine PagerDuty Runbook Automation licenses to companies, with Brazilian invoicing, local contracting in Portuguese and full legal compliance — the safe way to buy imported software under a Brazilian corporate entity, with no risk of irregular licensing.
When you buy PagerDuty Runbook Automation OSB Software, you get:
- Consultative, specialist support — specialists who size your named user licensing to your actual operation, avoiding over- or under-buying.
- Fast, secure processes — purchase order to delivery of genuine licenses, traceable at every step.
- Dedicated commercial follow-up — quote to delivery and renewal, with advance notice before your license expires.
- Invoicing that fits your company — Brazilian invoicing and terms adapted to your corporate procurement process.
- Proven track record — thousands of customers served across Brazil.
If you are looking for where to buy PagerDuty Runbook Automation in Brazil with legal certainty and properly licensed imported software, request a quote: OSB Software delivers reliable technology, qualified support and a simple, transparent purchase.
