CI/CD pipeline setup
NDDev sets up CI/CD and the server environment for your applications: builds and checks on every code change, release of a new version after merge, containers, backups and monitoring. Our own CI runs on GitHub Actions, and we publish our libraries of reusable checks as open source. NDDev has been working since 2019.
Who it is for
Teams that build and deploy by hand on the server, and companies launching a product that want to ship updates by clear rules from day one.
- GitHub Actions, GitLab CI or Jenkins
- Docker Compose, Kubernetes when load calls for it
- Backups and server hardening
- Monitoring with Prometheus and Grafana
The road every code change travels
Every change goes the same way: build, linters, tests, dependency and secret checks, image build and deployment. Images get versioned tags, are built in several stages and run as an unprivileged user, with health checks and resource limits.
- application deployment and containerisation with Docker
- server setup and hardening: firewall, key-only login, fail2ban
- a build, test and release pipeline on GitHub Actions
- separate development and production environments
- scheduled backups of the database and files
- Nginx, SSL certificates and domains
- infrastructure as code with Terraform or Ansible
- monitoring, Sentry and Telegram alerts as a separate service
We roll out a new version in one of three ways: replacing instances gradually, switching between two copies of the environment, or releasing to a small share of users first. We choose the method by load and by the cost of a mistake. In our open CI and CD libraries we describe a release as a chain of plan, approval, apply, verification and rollback, and we bring the same order to client projects.
How we put your releases in order
Inspection
We look at how the application is built and deployed today, where the secrets live and what would happen if the server failed today.
Containers and environments
We move the application into Docker, separate development from production and set up the server and backups.
Pipeline
We build the build, check and release pipeline and run several real releases through it together with your team.
Handover
We hand over access, an infrastructure description and a release guide, and from then on your team ships updates itself.
Questions about CI/CD and servers
Do we need Kubernetes?
Most projects do well with Docker Compose on one or two servers. We propose Kubernetes when load and the number of services call for it, and we explain up front what keeping it running will cost.
Will GitLab CI work?
Yes. Our main tool is GitHub Actions, and we also work with GitLab CI and Jenkins. If you already have a pipeline, we build on it.
Can you tidy up a server that is already live?
Yes. We work out what runs and how, move applications into containers and add backups and automated releases, and the live version keeps serving users the whole time.
Who pays for the servers?
Your company pays for hosting, and the accounts are in its name. In Kazakhstan we suggest ps.kz, for other countries DigitalOcean or Hetzner, and we also work with AWS, GCP and Azure.
How much does CI/CD set-up cost?
The price block shows where pricing starts. The final figure depends on how many services and environments you have, what goes into the pipeline and whether you need backups and monitoring. We fix the scope and timeline in the specification.
from $890
- Free warranty
- 8 days
Prices are starting prices for information only and are not a public offer. The final price is fixed in the specification.
Infrastructure and launch
Related
Tell us how a new version ships today
Describe your stack, your server and who deploys updates and how. We will outline the work and give you a price.
We reply within 24 hours