Moving off Codeship: 7 alternatives, priced and mapped
CloudBees discontinued CodeShip on January 31, 2026: its retirement notice said the service would be fully decommissioned and become inaccessible, and the CloudBees end-of-life page now says the product is no longer supported. CloudBees points former customers to CloudBees Unify, which is sold on a custom quote. Either way your pipelines have to be re-authored somewhere, so below is what each landing spot costs at three team sizes and where every Codeship concept goes.
Codeship Basic and Codeship Pro are both gone, so you have to move:
- Cheapest at every size we priced → GitHub Actions: $0, $108 and $588 a month at 2,000, 20,000 and 100,000 Linux minutes.
- Closest hosted-CI feel → CircleCI ($0 / $180 / $885) or Semaphore ($0 / $135 / $735, no per-user fee).
- Already on GitLab → GitLab CI/CD keeps repo and CI in one place, at $20 / $390 / $1,625.
- Came from Codeship Basic's UI → Buddy's visual editor is the nearest fit, usage-billed at $111.88 / $252.80 / $693.
Cost at real volumes
What moving off Codeship costs at 2,000, 20,000 and 100,000 build minutes
The same three workloads priced on every tool's own list prices, on its 2-vCPU Linux machine, at the cheapest plan that fits, as monthly US-dollar amounts before tax. Codeship itself is not in the table because it can no longer be bought.
| Tool | Billing unit | Small: 2,000 min · 5 users · 2 concurrent | Medium: 20,000 min · 10 users · 5 concurrent | Large: 100,000 min · 25 users · 10 concurrent |
|---|---|---|---|---|
| GitHub Actions | Per minute: Linux 2-core $0.006/min; Free includes 2,000 min/mo | $0/mo Free: 2,000 min included |
$108/mo Free + 18,000 × $0.006 (Team at $4/user would be $142) |
$588/mo Free + 98,000 × $0.006 (Team would be $682) |
| GitLab CI/CD | Per seat + compute minutes: $10 per 1,000 extra min | $20/mo Free (max 5 users): 400 included + 2 packs × $10 |
$390/mo Premium 10 × $29/user (billed annually) + 10 packs × $10 |
$1,625/mo Premium 25 × $29/user (billed annually) + 90 packs × $10 |
| CircleCI | Credits: Docker Medium (2 CPU, 4 GB) = 10 credits/min; $15 per 25,000 credits | $0/mo Free: 20,000 of 30,000 credits |
$180/mo Performance: 200,000 compute + 5 extra users × 25,000 credits, minus 30,000 included = 12 blocks × $15 |
$885/mo Performance: 1,000,000 + 20 × 25,000 credits, minus 30,000 = 59 blocks × $15 |
| Buddy | Plan + seats + usage: $0.00024 per CPU-minute and per GB-minute; 2 vCPU + 4 GB = $0.00144/min | $111.88/mo Pro $29 + 4 seats × $20 + 2,000 × $0.00144 |
$252.80/mo Pro $29 + 9 × $20 + 3 concurrents × $5 + $28.80 usage |
$693/mo Pro $29 + 24 × $20 + 8 concurrents × $5 + $144 usage |
| Semaphore | Per minute, no seat fee: Linux x64 2 vCPU $0.0075/min; $15 of credits free each month | $0/mo 2,000 × $0.0075 = $15, covered by the $15 credit |
$135/mo 20,000 × $0.0075 − $15 credit |
$735/mo 100,000 × $0.0075 − $15 credit |
| Buildkite (hosted agents) | Per active user + vCPU minutes: $0.004/vCPU-min, small Linux (2 vCPU) = $0.008/min | $150/mo Pro 5 × $30; 4,000 vCPU-min included covers it (Free caps at 2,000 vCPU-min) |
$444/mo Pro 10 × $30 + 36,000 vCPU-min × $0.004 |
$1,534/mo Pro 25 × $30 + 196,000 vCPU-min × $0.004 |
| Woodpecker CI | Open source (Apache 2.0), self-hosted: no license fee | $0 license plus your servers and upkeep (not priced) |
$0 license plus your servers and upkeep (not priced) |
$0 license plus your servers and upkeep (not priced) |
| CloudBees Unify (vendor's path) | Custom quote only | Contact sales (no public price) | Contact sales (no public price) | Contact sales (no public price) |
Formula: plan or seat fees + (build minutes beyond the included allowance × the 2-vCPU Linux rate), rounded up to each vendor's purchase unit (CircleCI 25,000-credit blocks, GitLab 1,000-minute packs). All prices are monthly; GitLab Premium is the monthly equivalent of annual billing. Buddy is the one vendor in this table that charges for concurrency, so only its row includes that fee. Excluded: storage, network egress, Docker layer caching, macOS and larger machines, annual-commit discounts and promotions. Its plan is listed at €29 on Buddy's site and billed at the same figure in dollars (EUR to USD 1:1).
Sources, checked 2026-11-05: CloudBees CodeShip end of life · CloudBees Unify pricing · GitHub plans · GitHub Actions runner pricing · GitLab pricing · CircleCI pricing · CircleCI credit price list · Buddy pricing · Semaphore pricing · Buildkite pricing · Woodpecker CI
The shortlist
7 places to move your Codeship pipelines
Ranked for teams leaving a simple hosted CI. Your Git host and how you configured Codeship (Basic UI or Pro YAML) matter more than the rank.
Built into the repo, with the lowest cost at all three workloads we priced ($0, $108, $588 a month). Codeship Pro services map to services: containers. Downside: YAML gets complex fast and there is no visual editor.
Repos, issues, CI/CD and security scanning in one platform; image: plus services: is the closest match to codeship-services.yml. Per-seat Premium pricing makes it the priciest here at 25 users ($1,625 a month).
Managed cloud CI with Docker executors and secondary service images, workflows and test splitting. Free covers our small workload; credit pricing ($180 and $885 at medium and large) takes some forecasting.
Managed CI/CD where you assemble pipelines from prebuilt actions in a UI (or YAML), which suits teams coming from Codeship Basic's web setup. Free plan; Pro is $29 plus seats and usage, so $111.88 to $693 a month across our workloads. Weakness: a smaller community and ecosystem than GitHub Actions or CircleCI, and usage-based billing to keep an eye on.
Simple config, per-minute billing and no per-user fee ($0, $135, $735). Its main-plus-service containers mirror Codeship Pro closely. Weakness: a smaller ecosystem than GitHub Actions, GitLab or CircleCI.
Control plane from Buildkite, agents on your hardware or on its hosted agents. Suits security-sensitive builds that must stay on your machines; per-user Pro pricing ($150 at 5 users) makes it the most expensive small-team option here.
Lightweight, Apache-licensed and free to self-host, with container-per-step pipelines close to Codeship Pro's model. Best if you want to own the whole stack and don't mind running the server and updates yourself.
Migration map
Where each Codeship concept goes
Codeship Pro kept its config in codeship-services.yml (Docker services) and codeship-steps.yml (commands run in those services); Codeship Basic kept the same ideas in the project settings UI. Here is the nearest equivalent in five of the alternatives.
| Codeship (Pro / Basic) | GitHub Actions | GitLab CI/CD | CircleCI | Buddy | Semaphore |
|---|---|---|---|---|---|
| Steps Pro: codeship-steps.yml entries (service + command) · Basic: setup and test commands |
steps: with run: in a job |
script: in a job |
steps: with run: in a job |
Actions in a pipeline (UI or YAML), commands run in a chosen Docker image | commands: in a job inside a block |
| Services Pro: codeship-services.yml (image/build, depends_on, environment) · Basic: preinstalled databases |
container: for the job image, services: for databases |
image: plus services: |
Docker executor: first image is primary, extra images are services | Services attached to an action (MySQL, PostgreSQL, Redis and others) | agent.containers: first is main, the rest are services |
| Parallel work Pro: type: parallel step groups · Basic: parallel test pipelines |
Separate jobs (parallel by default), needs:, matrix |
Jobs in one stage, needs:, parallel: |
Workflow jobs without requires, parallelism |
Parallel actions or matrix | Jobs in a block run in parallel, parallelism |
| Branch rules Pro: tag: / exclude: regex on steps · Basic: deployment pipelines per branch |
on: push: branches, if: |
rules: on $CI_COMMIT_BRANCH |
filters: branches on workflow jobs |
Pipeline trigger per branch or wildcard, plus trigger conditions | promotions with auto_promote, block run.when |
| Secrets Pro: encrypted_env_file + codeship.aes key (Jet CLI) · Basic: environment variables in project settings |
Repository or environment secrets | CI/CD variables (masked, protected) | Contexts and project environment variables | Encrypted variables at workspace, project or pipeline level | secrets: attached to blocks |
| Caching Pro: cached: true image cache per branch, default_cache_branch · Basic: dependency cache |
actions/cache; Docker layer cache via build actions |
cache: keys |
save_cache / restore_cache |
Built-in pipeline cache (filesystem and Docker) | cache store / cache restore |
| Image push and approvals Pro: push steps to a registry, manual approval steps · Basic: deployment pipeline commands |
Docker build-push action; environments with required reviewers | docker build/push jobs; when: manual |
setup_remote_docker + push; type: approval job |
Build and Push Docker Image actions; Approval action | Docker commands in a job; manually started promotions |
Two things do not carry over. The codeship.aes key and encrypted_env_file only work with Codeship's Jet CLI, so re-enter every secret in the new tool's store and rotate it while you are there. Codeship's local jet steps run has no direct equivalent; test the new pipeline on a branch before pointing deployments at it.
Sources, checked 2026-11-05: CodeShip retirement notice (archived) · GitHub Actions docs · GitLab CI/CD YAML reference · CircleCI configuration reference · Buddy pipelines docs · Semaphore docs
Method
How we checked
On 5 November 2026 we confirmed the shutdown on CloudBees' own pages: the current end-of-life notice, an archived copy of the retirement notice that gives the January 31, 2026 date, and the fact that app.codeship.com and codeship.com/pricing now redirect to CloudBees pages. The same day we read every price in the cost table from the vendor's public pricing page and did the arithmetic shown under the table; nothing is estimated. The migration map comes from archived Codeship Pro and Basic documentation and each target tool's current configuration reference.
Common questions
Leaving Codeship: common questions
When did Codeship shut down?
CloudBees discontinued CodeShip on January 31, 2026. Its retirement notice said the service would be fully decommissioned and become inaccessible after that date, and the CloudBees documentation now states that it no longer supports the product. Both Codeship Basic and Codeship Pro were covered, so there is no edition left to stay on.
Which Codeship replacement costs least at each workload?
On list prices, GitHub Actions, CircleCI and Semaphore all cost $0 a month at our small workload (2,000 Linux minutes, 5 users). At 20,000 minutes GitHub Actions is cheapest at $108 a month, and at 100,000 minutes it is still lowest at $588, with Buddy next at $693. Woodpecker CI has no license fee, but you pay for and run the servers yourself.
Is CloudBees Unify a drop-in replacement for Codeship?
No. CloudBees recommends Unify to former CodeShip customers, but its pricing page offers a custom quote only, and the CloudBees migration guide has you translate pipelines into new YAML workflows and move secrets across by hand. That is the same re-authoring work as moving to any other CI, so compare it on the same terms.
How do I migrate codeship-services.yml and codeship-steps.yml?
Treat codeship-services.yml as the list of containers a job needs: the service you build in becomes the job image, and databases or other dependencies become service containers. Each entry in codeship-steps.yml becomes a step or job running the same command, tag and exclude patterns become branch filters, and parallel groups become jobs that run side by side. Re-enter secrets in the new tool's secret store and rotate them, because the codeship.aes key and encrypted_env_file have no equivalent elsewhere.
I used Codeship Basic, not Pro. Which alternative is closest?
Basic projects were set up in the web UI with setup commands, test pipelines and per-branch deployment pipelines, so the closest feel is a tool with a visual editor or very short config. Buddy lets you assemble the pipeline in a UI editor, while Semaphore and CircleCI keep the YAML short. Pro users who already think in Docker services map most directly to GitHub Actions, GitLab CI/CD or CircleCI; staying on Codeship is not an option for either edition.
Are there free Codeship alternatives?
Yes. GitHub Actions includes 2,000 minutes a month, CircleCI 30,000 credits for up to 5 active users, GitLab 400 compute minutes, Semaphore $15 of monthly credits, and Buildkite 2,000 vCPU minutes for up to 5 users; Buddy also has a free plan. Woodpecker CI is open source and free to self-host if you run the server yourself.