DEVOPS
Orphaned Preview-Namespace Reaper with Cost Threshold Paging
Scans cloud preview namespaces for ones with no recent activity, and when their combined spend crosses a threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionList preview namespaces + cost/activityShell
- LogicFilter idle; sum cost vs threshold
- ActionPage on-call to approve teardownPagerDuty
- ActionTear down approved idle namespacesShell
- OutputResolve incident + post reclaimed costSlack
What it does
Inspects ephemeral preview namespaces/buckets, flags those with no traffic or writes past a quiet period, and sums their ongoing cost. When idle spend crosses a budget threshold it escalates to the on-call engineer via PagerDuty rather than silently deleting, then tears down on approval.
When to use it
Use when forgotten preview stacks are quietly burning real money and you want a human gate keyed to cost, not just age. Suited to teams with a budget line for ephemeral infra and an on-call rotation that owns spend.
How it works
- 1A daily schedule starts the sweep.
- 2Use a shell step to list preview namespaces and pull each one's last-activity timestamp and accrued cost.
- 3A filter keeps namespaces idle beyond the quiet period.
- 4A logic step sums idle cost; if it exceeds the threshold, trigger a PagerDuty incident to the on-call owner with the list and an approve link.
- 5On acknowledgement/approval, run the teardown shell step to delete the idle namespaces.
- 6Resolve the PagerDuty incident and post the reclaimed-cost total to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect ShellRun sandboxed commands inside the workspace.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.