DEVOPS
Flag Lighthouse regressions against the production baseline
Audits each Vercel preview, compares its Lighthouse scores to the current production baseline stored in Postgres.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionRun Lighthouse audit on preview URLBrowserbase
- ActionFetch production baseline metricsPostgres
- LogicCompute deltas vs allowed drift
- OutputOpen Linear regression issue and hold deployLinear
What it does
Instead of a fixed score threshold, this gate measures change. It audits the preview, looks up the latest production baseline from a Postgres table, and computes the delta per metric. A small dip is tolerated; a regression past your allowed drift blocks promotion and files a Linear issue assigned to the PR author with the before and after numbers.
When to use it
Use this when absolute Lighthouse targets are unrealistic for a heavy app but you still want to stop any single PR from making things measurably worse. Great for teams optimizing incrementally where the rule is do no harm.
How it works
- 1A Vercel deployment-ready webhook fires with the preview URL and commit SHA.
- 2A Lighthouse run audits the preview and records LCP, CLS, TBT, and category scores.
- 3A Postgres query fetches the current production baseline metrics.
- 4A logic step computes per-metric deltas and checks them against the allowed drift.
- 5If a regression exceeds the budget, a Linear issue is opened with the diff and the deploy is held; otherwise the new scores are written back as the candidate baseline.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 4Connect LinearIssues, projects, cycles, triage.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.