DEVOPS
Vercel Preview Performance Budget Gate
Audits each Vercel preview deployment for page-load performance and accessibility against defined budgets.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeededVercel
- LogicFilter to preview builds on an open PR
- ActionMeasure perf and a11y metrics in headless browserBrowserbase
- LogicCompare metrics against budgets, flag breaches
- OutputPost scorecard and set perf-budget commit statusGitHub
What it does
Guards performance and accessibility on every preview. After a preview deploys, a headless browser measures load metrics (first contentful paint, total blocking time, accessibility score) on the preview URL and compares them to your budgets. If anything blows the budget, the PR is blocked with a scorecard showing exactly which metric regressed and by how much.
When to use it
Use it when speed and a11y are product requirements and you want a hard gate that stops a slow or inaccessible page from merging, rather than discovering the regression in production.
How it works
- 1Vercel emits a deployment-succeeded webhook with the preview URL and commit SHA.
- 2A filter limits the run to preview builds on an open PR.
- 3Browserbase loads the key pages and captures performance and accessibility metrics.
- 4Logic compares each metric to its budget and flags any breach.
- 5GitHub receives a `perf-budget` commit status and a scorecard comment listing measured values versus budgets, blocking merge on any failure.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 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
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.
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.
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.
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…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.