# DevOps and CI/CD implementation

Canonical: https://appagentix.co.uk/services/devops-cicd-implementation/

DevOps and CI/CD implementation for UK software and app teams. We set up CI/CD pipelines, Terraform, environments and app store releases as part of our DevOps implementation services. We build the path from pull request to production, then hand every account to you.

- First pipeline in 3 to 6 weeks, with 3 months of fixes
- Production releases wait for a named person to approve
- Repositories, secrets and Terraform state stay in your name

## What DevOps and CI/CD implementation costs, and how long it takes

We set up build and test pipelines, approved releases with rollback, Terraform, environments and mobile release lanes. A first pipeline costs £6,000 to £15,000 excluding VAT and takes 3 to 6 weeks. A fuller set-up with infrastructure as code and monitoring takes 6 to 10 weeks. Every account and secret sits in your name, and fixes are included for 3 months. A separate discovery and audit takes 2 weeks and ends in a written plan and fixed quote.

- Fuller set-up: 6 to 10 weeks
- First pipeline: 3 to 6 weeks
- Fixes after handover: 3 months included

## DevOps implementation services we deliver

DevOps consultants build the path from code to customer and teach your team to run it, and our work comes in six parts, each with a check you can test.

### Build and test pipeline

Every pull request is built and tested, and dependencies come from a cache keyed on your lock file, so runs stay short.

A timed log of the last 20 runs.

### Release and rollback

A concurrency group lets only one production deploy run at a time.

A rollback drill, timed before handover.

### Terraform

Servers and networks written as code. State is stored remotely and locked while it is written.

State in your cloud account, never on a laptop.

### Environments

Staging and production, plus a preview for each pull request if you want one.

Production secrets released only after approval.

### Mobile release lane

iPhone and Android builds signed and sent to testers by the pipeline.

No release depends on one laptop.

### Monitoring and alerts

Errors, response times and failed jobs raise alerts after each release.

Each alert names who it reaches and what to check.

## How a change reaches production, and what stops it

The stage map we build into every pipeline. Each stage has one rule that holds a release back.

1. **Pull request.** Stops on a failed build or no review
2. **Build and test.** Stops on any failing unit or API test
3. **Security checks.** Stops on a leaked secret or a flawed package
4. **Preview and staging.** Stops on a failed smoke test
5. **Approved release.** Stops until a named reviewer approves
6. **Watch and roll back.** An alert restores the last good version

The last step feeds the first: the loop repeats.

## Which tool is best for CI/CD pipeline?

Usually the one beside your code. Our rule of thumb, by situation.

Which tool fits your situation?

- If Your code is on GitHub, choose **GitHub Actions**. Jobs get short-lived cloud tokens through OpenID Connect, so no cloud keys are stored in GitHub.
- If Your code is on GitLab, choose **GitLab CI/CD**. One file in the project root sets the stages and jobs, and ID tokens sign jobs in to cloud services.
- If You run Jenkins or Azure DevOps and it works, choose **Keep it**. Moving rarely pays, so we add the missing stages, approvals and rollback.
- If Your project is open source, choose **GitHub Actions**. Standard hosted runners are free in public repositories.
- If Several services, each released on its own, choose **Kubernetes**. A rolling update keeps at least 75% of pods running by default, and one undo command restores the last revision.
- If One app and an API, with steady traffic, choose **No Kubernetes yet**. A managed platform or container service has fewer parts to run after handover.

## CI/CD pipeline setup for iPhone and Android apps

Each release step, its tool and its credential. Every account belongs to you.

| Release step | Tool and credential |
| --- | --- |
| Share one signing identity | Fastlane match, with certificates in a private Git repo, Google Cloud or Amazon S3 that you own. Run read-only in the pipeline, as Fastlane advises, so it never makes new certificates. |
| Sign in to App Store Connect | A Team API key from your account. No two-factor prompt. The key file downloads once, so it goes straight into your secrets. |
| Send the iPhone build to testers | upload_to_testflight, with the same key |
| Send the Android build to testers | upload_to_play_store to a test track, as a service account in your Google Cloud project. We use Workload Identity Federation where we can, so no service account key is stored. |
| Release to the public | You promote the tested build |
| Pay for build minutes | macOS for the iPhone build only. As of November 2026, GitHub bills a macOS minute at $0.062 and a standard Linux minute at $0.006. |

## The delivery report you sign off at handover

Filled in for our worked example, a UK booking company with a web app, an API and phone apps. An example, not a client.

**Delivery report, booking company, week 6**

| Check | Result | What we found | Next step |
| --- | --- | --- | --- |
| Pull request checks | Pass | Median 8 minutes over 20 runs | None |
| Cloud access | Pass after fix | A long-lived deploy key in repository secrets, replaced with short-lived tokens | Old key revoked in week 3 |
| Rollback drill | Pass after fix | Took 19 minutes: no backup check before the database step. Added; second drill 6 minutes | Repeat each quarter |
| Actions pinned to a full commit | Pass | Every outside action pinned, as GitHub advises | None |
| Preview per pull request | Open | API previews need a test database with sample bookings | Your lead picks the data |
| Android build to a test track | Open | A former developer is still a Play Console admin | You remove them, we test again |

Handover waits until every row passes, or you accept an open row in writing.

## What we do not automate without a person approving

On GitHub, as of November 2026, required reviewers on a private repository need the Enterprise plan. Free, Pro and Team offer them on public repositories only, so on those plans we agree another approval gate in week 1.

- **Production deploys.** One of up to 6 named reviewers approves, and nobody approves their own run.
- **Production secrets.** Released to a job only after its approval rules pass.
- **Admin bypass.** Switched off, so administrators follow the same rules.
- **Terraform apply.** A person reads the saved plan first. Plan files can hold secrets in plain text, so we guard them.
- **Data-changing migrations.** A person checks the backup result before data is deleted or rewritten.
- **Store releases.** Builds reach testers by themselves; going live is your call.
- **Breaking a state lock.** Never scripted. HashiCorp warns it can leave more than one writer.

## Five DORA measures: your baseline sheet

DORA now publishes five delivery measures, not four, and in week 1 we fill this sheet from your own records. Example figures for the booking company, last 90 days.

**Delivery baseline, booking company, week 1**

| Measure | Where the figure comes from | Week 1 |
| --- | --- | --- |
| Change lead time | Commit time in Git to deploy time in the pipeline log | 9 days (median) |
| Deployment frequency | Production deploy jobs | 8 in 90 days |
| Failed deployment recovery time | Incident start and fix times | 4 hours (median) |
| Change fail rate | Deploys followed by a rollback or hotfix | 2 of 8 (25%) |
| Deployment rework rate | Unplanned deploys caused by an incident | 2 of 8 (25%) |

DORA warns against turning these into targets, so we track the trend for one app and fill the sheet again in month 3.

## How do you implement a CI/CD pipeline?

In six weeks, in this order. For the booking company in our worked example, with twelve developers on GitHub Enterprise Cloud, this is 31 days of work at a fixed £15,500, excluding VAT. Price your own set-up with the calculator on this page.

### Week 1 baseline and risk list (Week 1)

We review your repositories, cloud account, access and recent releases.

You receive: An audit note, the baseline sheet and a risk list.

### Pipeline and tests (Weeks 2 to 3)

Build, tests and security checks run on every pull request.

### Environments and IaC (Weeks 3 to 5)

Staging and production in Terraform, with locked remote state and short-lived cloud access.

### Release lane and rollback (Weeks 5 to 6)

Approvals, the mobile lane if you have an app, and a timed rollback drill.

### Handover and training (Week 6)

A working session with your team. We remove our access when you say so.

You receive: The delivery report, a runbook and the account list.

## Estimate your DevOps and CI/CD set-up in a minute

Pick what your first version needs.

Audit, one pipeline for one app, staging and production, rollback: £6,000 to £12,000, 3 to 5 weeks.

### Pipeline platform

- GitHub Actions: included
- GitLab CI/CD: included
- Your Jenkins or Azure DevOps: included

### Environments

- Staging and production: included
- Plus a preview per pull request: £2,500 to £4,000

### Hosting target

- Your servers or a managed platform: included
- Containers on a managed service: £2,500 to £4,000
- Kubernetes: £6,000 to £10,000

### Add to the pipeline

- Terraform for one cloud: £4,000 to £6,000
- Mobile release lane: £3,000 to £6,000
- Unit and API test stages: £3,000 to £5,000
- End-to-end tests: £4,000 to £6,000
- Dependency, secret and image scans: £2,000 to £3,500
- Monitoring, logs and alerts: £3,000 to £5,000
- Database migration with backup check: £2,000 to £3,000
- Rollback drill and runbook: £1,500 to £2,500
- Cloud cost and permissions review: £1,500 to £2,500
- DORA measures dashboard: £2,000 to £3,500
- Team workshop, two half days: £1,000 to £1,500

An estimate, not a quote, excluding VAT. Priced at £500 a day; the fixed price follows the audit.

## DevOps services UK teams own at handover

What moves into your accounts, and what the price leaves out.

- **Repositories and pipeline files.** In your organisation from the first commit; our team are users you can remove.
- **Cloud access.** A trust link for short-lived tokens. No long-lived keys left behind.
- **Secrets.** Stored in your account. You get the names; values never travel by email.
- **Terraform state.** A backend in your cloud account that supports state locking.
- **Build minutes.** Billed by GitHub to the repository owner, which is you, in US dollars.
- **Signing and store access.** The signing store, App Store Connect key and Play service account.
- **Our refund promise.** If we do not deliver what the written scope promises, we refund what you paid for the undelivered work within 7 days.
- **Not in the price.** Cloud, GitHub and app store bills, and on-call cover outside the support plan.

## Apps we have built and the set-up behind them

A few examples from the many apps we have built, with the containers, pipelines and cloud hosting each one runs on.

### Amara Social

Social and creator apps

Amara Social is a creator app our team built in React Native, with a Node.js backend serving REST APIs over PostgreSQL and Redis. The backend runs in Docker containers, and Docker and CI/CD pipelines are part of the stack we put in place.

[Read the Amara Social case study](https://appagentix.co.uk/our-work/amara-social/)

### Streaming service app: cloud hosting and video delivery

Media and streaming

Our team built this streaming service app on AWS, where a Node.js backend and a MongoDB database serve the Flutter app. Films, series and live channels are held in cloud media storage and reach viewers as HLS streams through a content delivery network. Role-based admin access, activity logs and encryption in storage and in transit protect accounts and payments.

[Read the Streaming service app case study](https://appagentix.co.uk/our-work/streaming-service-app/)

## DevOps and CI/CD implementation questions

### What is DevOps as a service?

An outside team builds and runs your delivery pipeline for a monthly fee. Ours covers fixes, updates and a monthly report after the build, with a 3-month minimum, then 30 days’ notice.

### Is CI CD the same as DevOps?

No. CI/CD is the automated path of building, testing and deploying each code change. DevOps is the wider way of working in which developers work closely with IT operations.

### What are the four stages of a CI/CD pipeline?

Red Hat describes a path of building, testing and deploying code, and GitLab’s own guide says typical stages might be build, test and deploy.

### Can you explain CI/CD pipeline in a simple way?

It is a conveyor belt for code, where each change is built and tested by itself, then shipped once the checks and a reviewer pass it. If a release goes wrong, the belt returns to the last good version.

### How much do consultants charge in the UK?

Advertised UK contract rates for DevOps engineers have a median of £525 a day (six months to 14 November 2026). We also supply a DevOps engineer by the day for hands-on work in your own pipeline.

### What is the cost of implementation?

For CI/CD, our first pipeline costs £6,000 to £15,000. Add running costs: build minutes billed by GitHub, and your cloud bill.

[UK app prices, line by line](/app-development-cost/)

## Related services

- [App maintenance and support](https://appagentix.co.uk/services/maintenance-support/)
- [Software modernisation](https://appagentix.co.uk/services/software-modernisation/)
- [Product engineering](https://appagentix.co.uk/services/product-engineering/)
- [Web app development company](https://appagentix.co.uk/services/web-app-development-company/)
- [Flutter app development](https://appagentix.co.uk/services/flutter-app-development/)
- [React Native app development](https://appagentix.co.uk/services/react-native-app-development/)

By [Jainendra Ojha](https://www.linkedin.com/in/jaizendra/), Co-Founder and CEO, AppAgentix. Reviewed November 2026.

[Book a call](https://appagentix.co.uk/requestaquote/)
