For teams on GitHub Actions and Cloudflare

Build failed. Buddy explains why. You approve the fix.

Buddy finds the cause, drafts the fix, and opens a pull request once you approve.

Get started Open the live demo

Read-only by default. Demo needs no sign-up.

DevOps Buddy home: the workspace brief, then the services that need attention, with the failing Storefront deploy at the top
Works with
  • GitHub Actions
  • Workers
  • Pages
  • D1
  • R2
  • KV
  • Zones and DNS

What happens when something fails

Nothing reaches your repo until you say yes.

  1. 1Root cause

    Buddy explains the failure

    With the log lines that prove it.

    Deploy failedacme/storefront · Deploy #1482 · 18 min ago

    Buddy· Root cause Dependency High confidence · 86 %

    The build fails: @acme/ui 4.0 no longer exports ./theme.

    Evidence
    1. 1
      [vite]: Rollup failed to resolve import "@acme/ui/theme" from "src/styles/tokens.ts".Deploy › build · line 25

    Buddy can be wrong. Check the evidence.

  2. 2Fix with Buddy

    You review the fix, then approve

    A diff you can read. A dialog that says what happens.

    Open a pull request with this fix?

    Nothing merges without a reviewer.

    What will happen
    • Creates branch buddy/fix-ui-tokens-7f3c
    • Opens a pull request against main
    Undo
    Reversible
    Access
    GitHub Contents: writeGitHub Pull requests: write

  3. 3Pull request

    Buddy follows up. You merge.

    If checks fail, it pushes a fix. It never merges.

    Pull request #212

    buddy/fix-ui-tokens-7f3c → main

    Checks passed· attempt 2 of 3 · waiting for review

    1. Buddy opened #212 on buddy/fix-ui-tokens-7f3c

    2. Checks failed: test (node 22)

    3. Buddy pushed a follow-up commit

    4. Checks passed

    5. Waiting for a reviewer to merge

Roll back from the incident, not the dashboard

Every action previews what changes before it runs.

  • Retry a failed Pages deployment
  • Roll Pages back to the last good deploy
  • Roll a Worker back one version
  • Re-run failed GitHub jobs
  • Deploy after a fix merges

Roll back Storefront production?

Production will serve the deployment from before the upgrade.

What will happen
  • Points shop.acme.dev at deployment 3f9a1c2
  • Keeps the failed deploy in history
Undo
Reversible
Access
Cloudflare Pages: Edit

Grouped by service, not by resource

Repos, Workers and databases, grouped into the services you run.

Services list: each service with its repos and Cloudflare resources, health for CI, deploys and runtime, and open incidents
Grouped from names, repos and bindings. Edit anything.

Read-only by default. Changes only with your approval.

Monitoring is read-only. Changes need a separate token and your approval.

  • A read-only guard on monitoring

  • Separate, opt-in write tokens

  • Approval for every action

  • Your branches stay yours

  • An audit log of every change

  • Encrypted, write-only secrets

Audit log

Settings › Audit log
ActionApproved byResultWhen
Opened pull requestacme/storefront #212ahmed@acme.devDone14:04
Pushed follow-up commit#212 · attempt 2 of 3ahmed@acme.devDone14:09
Rolled back Pagesstorefront → 3f9a1c2ahmed@acme.devDone14:21

Set up in about five minutes

No agent. No YAML.

  1. 1

    Create a workspace

  2. 2

    Connect read-only tokens

  3. 3

    Review your services

  4. 4

    Add write access Optional

Get started Read the setup guide

Watch one failure go from red to reviewed

One broken deploy, from red to reviewed.

The product tour is being recorded

Until then, try the live demo.

Open the live demo

Open the live demoRead-only. No sign-up.

Questions

More in the getting started guide.

What access do you need?

Read-only GitHub and Cloudflare tokens. Write access is optional. Scopes

Can Buddy change anything in my accounts?

Only with a write token, and only after you approve each action.

What if the fix is wrong?

It's a normal pull request. Review it, change it or close it.

What data do you store, and what does the AI see?

Encrypted connections and the audit log. The AI sees log excerpts, never your tokens. Details

How much does it cost?

Pricing will be announced soon.

Is this made by GitHub or Cloudflare?

No. It's independent.

Your next red build, explained.

Connect read-only tokens. See your services in minutes.

Get started Open the live demo