Website • Releases • Documentation
Meet Ctrlplane, an open-source deployment tool that automates multi-cloud, multi-region, and multi-service software deployments.
The easiest way to get started with Ctrlplane is by creating a Ctrlplane Cloud account.
If you would like to self-host Plane, please see our deployment guide.
| Installation methods | Docs link |
|---|---|
| Docker |  |
| Kubernetes |  |
- Unified Control: Centralize management of multi-stage deployment pipelines across diverse environments.
- Flexible Target Support: Deploy to Kubernetes, cloud functions, VMs, or custom infrastructure from a single platform.
- Advanced Workflow Orchestration: Automate sophisticated deployment processes including testing, code analysis, security scans, and approval gates.
- CI/CD Integration: Seamlessly connects with Jenkins, GitLab CI, GitHub Actions, and other popular CI tools to trigger deployments.
- Environment Management: Efficiently handle transitions between dev, test, staging, and production environments.
Development system must have docker engine installed and running.
- Clone the code locally using:
git clone https://github.com/sizzldev/ctrlplane.git - Switch to the code folder:
cd ctrlplane - Create your feature or fix branch you plan to work on using:
git checkout -b <feature-branch-name> - Open the code on VSCode or similar equivalent IDE.
- Copy
.env.exampleto.envfiles available in various folders. - Run the docker command to initiate services:
docker compose -f docker-compose.yaml up -d - Run
pnpm db:pushto push the schema to the database. - Run
pnpm devto start the development server.
You are ready to make changes to the code. Do not forget to refresh the browser (in case it does not auto-reload).
Thats it!
The Ctrlplane community can be found on GitHub Discussions, and our Discord server
Ask questions, report bugs, join discussions, voice ideas, make feature requests, or share your projects.
If you believe you have found a security vulnerability in Plane, we encourage you to responsibly disclose this and not open a public issue. We will investigate all legitimate reports.
Email [email protected] to disclose any security vulnerabilities.
