How Serverless‑cd Enables Low‑Cost, Elastic CI/CD on a Serverless Architecture

Overview

Serverless‑cd is an open‑source CI/CD framework that runs entirely on a serverless architecture. It is part of the Serverless Devs project, a CNCF sandbox incubator, and provides a low‑cost, elastic, and secure pipeline platform for developers who want to focus on business value.

Problems with Traditional CI/CD

Low resource utilization – build machines must be provisioned in advance and remain idle when no jobs run.

Task queuing – insufficient resources cause long wait times during peak build periods.

Poor isolation – a heavy task can consume CPU/Memory and cause other jobs to fail.

Security concerns – code repositories and build machines often share a public network, exposing them to attacks; shared ECS instances allow one application to access another’s code.

Key Characteristics of CI/CD Pipelines

Event‑driven – pipelines are triggered by webhooks or manual API calls.

Business‑driven workload peaks – build activity spikes during work hours and drops after hours, making capacity planning difficult.

Advantages of a Serverless‑Based CI/CD

Automatic elasticity – each build runs in a fresh instance, eliminating resource contention and queueing.

Pay‑per‑use – you are charged only for actual build execution, avoiding idle costs.

Zero operational overhead – the platform handles scaling and resource scheduling, letting developers focus on code.

Technical Architecture

Serverless‑cd follows a classic Master‑Worker model:

Master function – an HTTP entry point that receives events, performs security checks (public‑key verification, optional VPC binding), and dispatches jobs.

Worker functions – event‑driven functions that execute the pipeline steps and can run for extended periods.

The architecture diagram is shown below:

Trigger Methods

Webhook auto‑trigger – configure conditions such as push to master or merge request to start a build.

Open API – all platform capabilities are exposed via RESTful APIs for custom integration.

CLI – the Serverless Devs CLI provides direct commands to invoke pipelines, with component‑based extensibility.

Custom Pipelines

Serverless‑cd supports three ways to define pipeline steps:

Shell scripts – the simplest and most widely used method.

zx scripts – JavaScript‑based shell scripting using the google/zx project (https://github.com/google/zx).

Custom NPM packages – reusable packages (e.g., DingTalk or Enterprise WeChat notifications, OSS uploads) published to the NPM registry.

name: "shell example"
steps:
  - run: echo Hello world

name: "zx example"
steps:
  - script: 'const listFile = await $`ls -la`; console.log(listFile)'

name: "npm package example"
steps:
  - run: @serverless-cd/dingding

Deployment Steps

Install Serverless Devs CLI (requires Node.js): npm install @serverless-devs -g (version >= 2.1.7).

Configure Alibaba Cloud credentials: s config add (see the Serverless Devs installation docs).

Initialize a project: s init serverless-cd.

Enter the project directory and deploy: cd serverless-cd && s deploy.

References

https://github.com/Serverless-Devs/cicd

https://github.com/Serverless-Devs/serverless-cd

https://docs.serverless-devs.com/serverless-devs/install

https://github.com/google/zx