CI/CD that runs on your own computer

CID builds, tests and deploys your projects from the machine you're sitting at, or over SSH to servers you already own. Trigger on push, on a schedule or by hand, share projects with your team, and watch every step live.

Create a free account

Download for Windows

v1.3.0 · 101 MB · other platforms

CID

storefront

Running 4 members

Workflows Runs Connections Environment Members

#42
deploy-prod · Fix rounding in checkout total
main · Started by Sara on SARA-LAPTOP
nowRunning
#41
test · Add order history page
main · Started by you on STUDIO-PC
1m 12sSuccess
#40
nightly-backup · Scheduled · At 04:00 AM
— · Started by schedule on BUILD-BOX
38sSuccess
#39
deploy-prod · Bump dependencies
main · Started by Kian on KIAN-MBP
22sFailed

Run #42

deploy-prod · main · a4c452c

Install12s
Test48s
Build31s
Deploy to prod-01…

$ rsync --changed-only ./dist prod-01:/srv/storefrontsending incremental file list  14 files changed, 3 removed$ pm2 reload storefront[PM2] Applying action reloadProcessId on app [storefront]

Runs on your own computer

Deploys over SSH, no agent

Shared projects with roles

Your code stays with you

Everything a pipeline needs

Your pipelines, without someone else's servers

No runners to rent, no YAML to push and wait on. Workflows run where your code already is, and every run is kept with its logs.

Workflows in a real editor

Each workflow is a trigger and an ordered list of steps. Write steps in a multi-line editor with syntax highlighting, drag to reorder, give a step its own working folder, and save & run in one click.

1Installnpm ci

2Testnpm test -- --ci

3Buildnpm run build

4Deployrsync -az ./dist prod-01:/srv/app

Run on this computer

Build installers, run tests and package releases right on your machine. No server needed.

Command PromptPowerShellGit BashBash on macOS & Linux

Deploy over SSH

Add servers, generate or import keys, and CID syncs only the files that changed over SFTP before running your steps. Nothing to install on the server, and a SOCKS5 proxy if your network needs one.

Push, schedule or click

Start runs on every push to a branch, on a cron schedule in plain English, or by hand.

On pushmain

ScheduleAt 04:00 AM

ManualRun

Live logs and full history

Follow colour-coded logs step by step with exit codes and timings. Filter history by workflow, status and date, and get a desktop notification when a run finishes.

$ npm test -- --ciPASS src/cart.test.jsPASS src/checkout.test.jsTests: 48 passed, 48 totalexit 0 · 48s

Variables & secrets

Per-project variables and encrypted secrets, passed to every step as environment variables.

Artifacts

Keep the installers, zips and reports a run produces, one click from the run that made them.

Keys stay encrypted

SSH private keys and secret values are stored encrypted, and only people with the right role can reveal them.

Teams

Share a project with the people you build it with

Invite teammates by email from a project's Members tab, pick their role, and they accept from the link, creating a CID account first if they need one.

Four roles, clear limits
Owners do everything. Admins edit the project and manage people. Members run and cancel workflows. Viewers read workflows, runs and logs.
Each push runs once
When several teammates have CID open, the first computer to pick up a push or a schedule runs it and the others skip it.
Runs stay on your machine
Everyone runs from their own copy of the repository. Folders, shells and artifacts stay per computer.

Read about teams and roles →

Members · storefront

Invite

Y
You
you@studio.dev
Owner
S
Sara Ahmadi
sara@studio.dev
Admin
K
Kian Rahimi
kian@studio.dev
Member
L
Lena Ford
lena@client.co
Viewer

deploy-prod #42 · push to main

Started by Sara on SARA-LAPTOP · ran once

How it works

From sign-up to your first green run in minutes

1
Create an account
Sign up here, then sign in to the desktop app with the same email and password.
2
Add a project
Point it at the repository on your computer. Add servers and SSH keys if you deploy.
3
Write a workflow
Pick a trigger and where it runs, then list the steps: the commands you'd type yourself.
4
Push and watch
Push, wait for the schedule or press Run, and follow the logs live, in the app or here.

deploy-prod · workflow

{  "name": "deploy-prod",  "trigger": "push",  "branch": "main",  "runsOn": "prod-01",  "steps": [    { "name": "Install", "run": "npm ci" },    { "name": "Build", "run": "npm run build" },    { "name": "Restart", "run": "pm2 reload storefront" }  ]}

Last run succeeded in 1m 31s · Started by you on STUDIO-PC

cid.pumpkins.dev/dashboard

Runs, 14 days

Success rate

92%

Projects

Activity

Succeeded Failed

Your dashboard on the web

Check on every run from any browser

Sign in here to see your projects, shared projects, workflows and run history, read the logs of any run, and manage your account, from any computer or phone.

Open your dashboard

Download