PagerDuty Runbook Automation Self-Hosted
Commercial runbook and operations-automation platform deployed as a customer-operated cluster in AWS.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Runbook Automation Docker CA trust-store remediation
Official Docker images before 6.3.0 trust compromised eMudhra intermediates. The vendor directs self-hosted operators to pull and redeploy fixed images.
Scope: Official Runbook Automation/Rundeck and Runner Docker images before 6.3.0. SaaS is excluded; host-installed RPM/DEB/WAR deployments depend on OS and Java trust stores.
An on-path attacker could exploit trusted compromised intermediates for outbound TLS. The vendor reports no known exploitation; this is not a flaw in Runbook Automation code.
Action: Redeploy the updated 6.3.0+ official images rather than patching a disposable container. For host installations update and verify both OS and Java trust stores and restart.
Primary source · Reviewed 2026-11-18
What lands where
Supplied by
Vendor or project
Commercial RPM/DEB/WAR or official Docker image on customer AWS infrastructure; obtain a current licensed Helm artifact before using the older EKS recipe
Runs in
Documented customer environment
Customer-operated Runbook Automation application with load balancing, database, object storage and execution nodes.
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer manages EKS or VMs, database, storage, networking, TLS, execution nodes, backups, upgrades and license delivery.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Runbook Automation Self-Hosted on AWS ↗ · Source checked 2026-11-18
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Commercial RPM/DEB/WAR or official Docker image on customer AWS infrastructure; obtain a current licensed Helm artifact before using the older EKS recipe |
|---|---|
| Infrastructure | Servers / containers The AWS architectures run persistent application and execution services backed by customer database and object storage. |
| Licensing model | Commercial Only Runbook Automation Self-Hosted is commercial software requiring a license. Rundeck Community is separately Apache-2.0 licensed and is not the selected edition. |
| License | Commercial PagerDuty Runbook Automation Self-Hosted license required; Rundeck Community is a separate Apache-2.0 edition. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
12 of 12 fields researched (100%) · 7 documented · 5 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery
The vendor confirms a separate commercial Self-Hosted product, but the reviewed PagerDuty Marketplace leads did not establish an exact offer entitling that software. SaaS subscriptions, professional services and remotely hosted runners are different scopes. Request the applicable self-hosted offer/order ID, seller, licence terms and current commercial artifact.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility
A commercial Runbook Automation licence file and AWS deployment do not establish cloud-commitment credit. Confirm the actual self-hosted order, procurement route and buyer agreement.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · AWS commitment qualification is product/agreement-specific ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Single sign-on
Edition-dependentEvidence and scope for Single sign-on
Runbook Automation’s commercial SSO integration uses OAuth2/OIDC authorization-code login, with configuration guidance for Okta, Ping and Azure AD and required signing-key discovery. Confirm identity/role mapping for the selected IdP; this is distinct from Rundeck Community authentication.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18
Edition-dependent · Editor reviewed.
- SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning
The OIDC SSO guide does not establish a commercial self-hosted SCIM endpoint or user/group lifecycle. PagerDuty account provisioning and SSO profile synchronization are not evidence of Runbook Automation SCIM support.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · Authentication providers are not a provisioning endpoint ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
PagerDuty says Runbook Automation Self-Hosted can operate inside the customer firewall to meet stricter requirements such as FedRAMP. That is deployment/control guidance, not evidence that the self-hosted product or buyer’s automation system has that authorisation. Obtain the actual report/certificate and include local database, runners, plugins, job targets, identity and operations in the assessment.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
The commercial SSO guide configures OIDC login and signing-key validation. Release 6.3.0 hardens webhook token storage and official container trust stores. Operators must separately control job permissions, key storage, runner credentials and target access.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · 6.3.0 security changes ↗ · Container CA trust-store advisory ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Air-gapped operation
Edition-dependentEvidence and scope for Air-gapped operation
PagerDuty explicitly identifies Runbook Automation Self-Hosted for air-gapped networks and operation entirely inside the customer’s infrastructure. Prepare the commercial application/runner/plugin artifacts, local database, identity, certificates and job targets. A valid commercial licence is still required; agree its offline issuance/renewal and expiry process rather than assuming the SaaS or cloud-runner flow is disconnected.
Commercial Runbook Automation Self-Hosted with prepared local dependencies; SaaS and remotely hosted control planes are excluded · Source ↗ · Local commercial licence installation ↗ · Reviewed 2026-11-18
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The current guide names the commercial image rundeckpro/enterprise:6.3.0 with an external database, and recommends a reviewed derived image in a private registry. DEB installation separately uses package rundeckpro-ent. The EKS tutorial’s linked commercial Helm directory returned 404; obtain a current chart rather than substituting its Community example.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · Customer AWS EC2/load balancer/RDS/S3 architecture ↗ · Commercial DEB package repository ↗ · EKS tutorial and obsolete chart link ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
Commercial Runbook Automation minimum is 4 CPUs/16 GB RAM with 12 GB heap per application instance; recommended is 8 CPUs/32 GB with 24 GB heap. Java 17 is the minimum from 6.0. Production uses an external supported database; H2 is for testing. HA replicas, logs and job runners add resources.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Commercial Runbook Automation Self-Hosted requires a licence file and quote. Rundeck Community’s Apache 2.0 licence does not license the commercial SSO/cluster features in this listing. Price runners, support and the purchased entitlement separately.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
- Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate
Specify concurrent jobs, execution duration, runner pools and job-target work, HA application instances, external database HA, log/object retention and commercial licences. The per-instance minimum is not a complete AWS bill for 100 users or 1 TB of logs.
Planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA; average usage without measured concurrency or throughput · Source ↗ · Current AWS Linux EC2 rates; workload/topology still required ↗ · Storage performance and charging inputs ↗ · Reviewed 2026-11-18
Sources checked — unresolved · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
The official release notes identify Runbook Automation/Rundeck 6.3.0 and its security fixes. The public Rundeck OSS tag v6.3.0 was published October 22, 2026; that repository timestamp is not asserted as a separate commercial-package publication time. Verify the licensed image/package version and rebuild official containers for the CA fix.
PagerDuty Runbook Automation Self-Hosted: selected customer-operated edition · Source ↗ · Commercial Docker remediation requirements ↗ · Reviewed 2026-11-18
Documented · Editor reviewed.
Scope & considerations
Commercial Runbook Automation Self-Hosted is distinct from PagerDuty SaaS and Rundeck Community. The EKS tutorial’s linked commercial Helm directory returned 404; use current licensed package/container documentation and obtain a pinned chart if needed. Official Docker images before 6.3.0 require the scoped CA trust-store remediation.
Category fit
- Workflow automation
- Automates operational runbooks, scheduled jobs and controlled actions through customer-operated execution services.
- DevOps
- Provides operations automation, job orchestration, access control and integrations for delivery and incident workflows.
Compare within Workflow automation
- Activepieces Self-HostedSelf-hosted workflow automation platform with integrations, triggers, actions and worker execution.
- AWS
- Google Cloud
- Railway
- Apryse FluentCustomer-hosted document-template management and rendering software for automated business output.
- AWS
- Azure
- Camunda 8 Self-ManagedCommercial self-managed process orchestration and workflow automation platform.
- AWS
- Azure
- Google Cloud
- CloudBolt Cloud Management PlatformSelf-hosted cloud-management and infrastructure-automation platform deployed as a customer-operated appliance.
- AWS
- Azure
- CortezaLow-code platform for business records, workflows and configurable CRM applications.
- Hostinger
- Decisions Self-HostedCommercial rules and workflow platform with provider-specific container deployments.
- AWS
- Azure
- Google Cloud
- Documenso Self-HostedSelf-hosted electronic-signature and document workflow application with a Railway deployment path.
- Railway
- DocuSeal Self-HostedSelf-hosted document forms and electronic-signature workflows with API and webhook integration.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Railway
- Render
- Heroku
- Linode
- Vultr
- Hostinger
- LumaDock
Showing 8 of 25 other listings in Workflow automation. These products address related workflows; read their category-fit notes before comparing scope. See all of Workflow automation →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Deploy Runbook Automation on Amazon EKS ↗docs.rundeck.com
- Runbook Automation Self-Hosted on AWS ↗docs.rundeck.com
- Deploy Rundeck on AWS with Terraform ↗docs.rundeck.com
- Runbook Automation licensing ↗docs.rundeck.com
- Rundeck and Runbook Automation editions ↗docs.rundeck.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Runbook Automation Self-Hosted on AWS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-18. Vendor support commitment: not assessed; confirm the selected release and contract.
PagerDuty documents a customer-operated HA architecture using AWS load balancing, RDS and S3; a separate guide deploys the product to customer EKS.
- Runbook Automation Self-Hosted on AWS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked