Camper: running security campaigns on Temporal

Temporal describes Camper, a workflow-based system built on Temporal to coordinate security and other cross-repository campaigns, where completion means every finding has a recorded outcome such as a merged fix, documented exception, archived repository, or rejected proposal. Developed after manual coordination across Jira, GitHub, scanners, and Slack proved time-consuming, Camper creates durable campaign and finding workflows that can discover issues, create tickets, generate or request changes, open pull requests, wait for CI and reviews, retry failures, and retain state through restarts. Campaign specifications define scope, approval requirements, integrations, remediation tools, policies, and target repositories, while allowing operators to update guidance or add targets during execution. Camper uses deterministic Deputy transformations for supported changes, Codex for context-dependent candidate fixes, or ticket-only workflows when human remediation is preferable, while keeping maintainers in control of review and merging. By September 29, 2026, it had opened at least 150 public pull requests across 72 Temporal repositories, with 111 merged, and a Release Engineering credential migration demonstrated its applicability beyond Security. Camper can run locally with simulated integrations or connect to Temporal Cloud using the same workflow model, though it remains private and early as Temporal develops operational tooling, credential boundaries, and documentation ahead of a planned open-source release.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.