TiloBox
Back to directory
Screwdriver CD project preview

Screwdriver CD

Open-source build platform and CI/CD engine designed for high-scale continuous delivery.

LicenseBSD-3-Clause
GitHub stars2.2k
Last commit1 weeks ago
Tags5 topics
Continuous DeliveryNodejsDevops InfrastructurePipeline EngineEnterprise Ci
Overview

Why consider Screwdriver CD?

Screwdriver CD is an open-source continuous delivery platform built for massive enterprise scale by Yahoo. It features pipeline workflow branching, metadata event propagation, rollbacks, and ephemeral container execution.

Guided learning

Learn Screwdriver CD by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of Screwdriver CD

Screwdriver CD manages complex deployment graphs and microservice dependencies with automated pull-request validation pipelines.

Installation

bash
1# Screwdriver in a Box (Local Docker)
2docker run -d -p 9000:9000 screwdrivercd/screwdriver:stable

Screwdriver CD is licensed under the BSD-3-Clause License.

Related tools

More options with a similar category or technology profile.

Screwdriver CD FAQs

Screwdriver CD is listed as a Developer Tools tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

Screwdriver CD is listed under the BSD-3-Clause license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

Screwdriver CD is listed as an alternative to Jenkins. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.