PagerDuty’s November 3, 2026 launch introduces Paige and the PD Reliability Platform alongside PD Labs. Its announcement places SRE Workbench, Deep Investigation and Topology in Labs. For a team considering the new investigation workspace, that label has practical consequences for support and evaluation.
PagerDuty’s November 3 launch explanation
Keep the experiment’s terms with the trial
PagerDuty’s PD Labs documentation describes an incubation platform before early access or general availability. It says experiments are not officially supported through PagerDuty’s support channels, and graduation to a later release stage is not guaranteed. Access uses an individual license: each user must accept the applicable product-specific terms. A colleague’s acceptance is not company-wide acceptance.
PD Labs access, support model and graduation policy
The SRE Workbench overview separately identifies it as a Labs experiment whose features and availability may change. It says Deep Investigation requires at least one configured observability data connector, and Topology requires the GitHub code tool. Record those requirements for the intended investigation rather than assuming access to a screen establishes access to the evidence behind it.
SRE Workbench availability and data prerequisites
Use a limited evaluation brief
Here is an original fictional planning example, not a PagerDuty test. A software team wants to explore a past training incident involving a demonstration service. Its evaluation brief identifies the incident, the question to investigate, the permitted demonstration data and the person responsible for supervising the exercise. It does not make the experiment a dependency for an upcoming live incident.
Before the session, ask the account administrator to confirm the permitted connector and data scope. Ask each participant to check the applicable access terms through their own account. Keep the support-model note beside the exercise plan so the team knows which assistance has actually been established. These are suggested planning steps, not evidence of a configured account.
Separate an available tool from an answered question
In the fictional session, the question is whether a deployment happened before a recorded alert. Write the expected evidence source in advance, then record whether the demonstration actually retrieves relevant timestamps and explains their relationship. If the evidence is absent, preserve the question as unanswered. A plausible explanation alone cannot supply the missing record.
Record any connector or access obstacle separately from the quality of an explanation. This helps the evaluator distinguish a prerequisite that needs attention from a conclusion that needs better evidence. Do not label an empty investigation a successful diagnosis merely because the workspace opened.
Recheck before widening use
Keep the evaluation date, current product documentation and unresolved questions together. If PagerDuty later changes the feature’s status or support arrangements, review the actual update before changing the deployment plan. No account, connector, incident investigation or remediation was tested for this article. The fictional exercise does not establish diagnostic accuracy or production readiness.