techlist.io
KREN
cloudflare

Run CI/CD for millions of repos — on your platform, on Cloudflare (opens in new tab)

cloudflareci-cdtypescriptwranglercloudflare-workflowsbunsandbox-sdk

Cloudflare is bringing code storage, CI, and deployment together on its platform. Its CI SDK turns Cloudflare Workflows into TypeScript-defined pipelines that can build, test, and deploy repositories stored in Artifacts. The approach supports both platform-managed CI for customer applications and custom workflows, while adding isolated execution, caching, parallelism, and optional AI-powered self-healing.

Cloudflare-Hosted CI/CD

  • Artifacts provides versioned code storage capable of supporting millions of repositories.
  • Artifact push events can directly trigger Workflow executions through a new events configuration field.
  • A CI job can:
    • Build code in an isolated environment
    • Run linters, typechecks, and unit tests
    • Cache dependencies between steps
    • Automatically fix failed steps with an AI review agent
    • Deploy only after successful validation

CI/CD as a Cloudflare Workflow

  • A traditional CI/CD pipeline is essentially an ordered sequence of Workflow steps.
  • Instead of complex YAML configuration, developers can define pipelines in TypeScript using step.do().
  • The CI SDK combines Workflows with the Sandbox SDK to run commands safely and independently.
  • Workflow retries and timeouts manage state and failures without requiring developers to call the Sandbox API directly.
  • Push-triggered jobs no longer require separately configuring event subscriptions, queues, and consumers.

Dependency Caching and Parallel Execution

  • An initial install step can download dependencies and tools such as bundlers, linters, and test runners.
  • Cache inputs can include files such as package.json and bun.lock.
  • The resulting sandbox snapshot is stored in an R2 bucket and reused by later steps.
  • Build, lint, test, and typecheck steps can run concurrently with Promise.all().
  • A deploy step runs only after all required checks complete successfully.

Platform-Managed and Custom CI

  • Platforms can define one reusable CI/CD pipeline for applications created by their customers.
  • Platform-owned code and customer code can use different pipelines while remaining in the same namespace.
  • Customers who need specialized behavior can define their own Workflow and run custom CI on their repository.
  • Both managed and custom CI pipelines can operate simultaneously.

Extensible and Self-Healing Pipelines

  • Developers can import CIWorkflow from @cloudflare/ci and define their own workflow.
  • Each build or validation step runs in a separate isolated sandbox.
  • Workflows can invoke an AI agent when a build fails.
  • The agent can diagnose issues, apply a fix, and push a commit for approval.
  • Cloudflare provides a self-healing CI example through Project Think.

Cloudflare’s recommended model is to treat CI/CD as ordinary TypeScript Workflow code: install dependencies once, run checks in parallel, and deploy only after success. This gives platforms a reusable default pipeline while preserving the flexibility for individual teams or customers to customize their own builds.