DevOps and CI/CD

DevOps and CI/CD 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

Security and compliance

  • Cyber EssentialsCertified
  • Cyber Essentials PlusIndependently tested
  • ISO/IEC 27001:2022Information security
  • ISO 9001:2015Quality management
  • ISO/IEC 42001:2023AI management
  • SOC 2 Type IIAudited controls
  • UK GDPR andData Protection Act 2018
  • ICORegistered
  • NHS DSPTData security toolkit
  • Level AA conformance, W3C Web Content Accessibility Guidelines 2.2WCAG 2.2 AAAccessibility
  • PCI DSSCard data security

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.

  • 01

    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.

  • 02

    Release and rollback

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

    A rollback drill, timed before handover.

  • 03

    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.

  • 04

    Environments

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

    Production secrets released only after approval.

  • 05

    Mobile release lane

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

    No release depends on one laptop.

  • 06

    Monitoring and alerts

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

    Each alert names who it reaches and what to check.

Still weighing up how to build your app? Ask the developers who would build it, before you commit to anything.

Book a free 30-minute call

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. 01Pull request

    Stops on a failed build or no review

  2. 02Build and test

    Stops on any failing unit or API test

  3. 03Security checks

    Stops on a leaked secret or a flawed package

  4. 04Preview and staging

    Stops on a failed smoke test

  5. 05Approved release

    Stops until a named reviewer approves

  6. 06Watch and roll back

    An alert restores the last good version

Step 06 feeds step 01: 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?

  • IfYour code is on GitHub

    ChooseGitHub Actions

    Jobs get short-lived cloud tokens through OpenID Connect, so no cloud keys are stored in GitHub.

  • IfYour code is on GitLab

    ChooseGitLab CI/CD

    One file in the project root sets the stages and jobs, and ID tokens sign jobs in to cloud services.

  • IfYou run Jenkins or Azure DevOps and it works

    ChooseKeep it

    Moving rarely pays, so we add the missing stages, approvals and rollback.

  • IfYour project is open source

    ChooseGitHub Actions

    Standard hosted runners are free in public repositories.

  • IfSeveral services, each released on its own

    ChooseKubernetes

    A rolling update keeps at least 75% of pods running by default, and one undo command restores the last revision.

  • IfOne app and an API, with steady traffic

    ChooseNo 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.

  • 01Release stepShare one signing identity

    Tool and credentialFastlane 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.

  • 02Release stepSign in to App Store Connect

    Tool and credentialA Team API key from your account

    No two-factor prompt. The key file downloads once, so it goes straight into your secrets.

  • 03Release stepSend the iPhone build to testers

    Tool and credentialupload_to_testflight, with the same key

  • 04Release stepSend the Android build to testers

    Tool and credentialupload_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.

  • 05Release stepRelease to the public

    Tool and credentialYou promote the tested build

  • 06Release stepPay for build minutes

    Tool and credentialmacOS 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.

ExampleDelivery report, booking company, week 6AppAgentix
CheckResultWhat we foundNext step
Pull request checksPassMedian 8 minutes over 20 runsNone
Cloud accessPass after fixA long-lived deploy key in repository secrets, replaced with short-lived tokensOld key revoked in week 3
Rollback drillPass after fixTook 19 minutes: no backup check before the database step. Added; second drill 6 minutesRepeat each quarter
Actions pinned to a full commitPassEvery outside action pinned, as GitHub advisesNone
Preview per pull requestOpenAPI previews need a test database with sample bookingsYour lead picks the data
Android build to a test trackOpenA former developer is still a Play Console adminYou 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.

ExampleDelivery baseline, booking company, week 1AppAgentix
MeasureWhere the figure comes fromWeek 1
Change lead timeCommit time in Git to deploy time in the pipeline log9 days (median)
Deployment frequencyProduction deploy jobs8 in 90 days
Failed deployment recovery timeIncident start and fix times4 hours (median)
Change fail rateDeploys followed by a rollback or hotfix2 of 8 (25%)
Deployment rework rateUnplanned deploys caused by an incident2 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.

Most app projects run late. More than 95% of ours are delivered on or before the agreed date, and yours can be next.

  • 95%+ delivered on or before the agreed date
  • 9 to 10 wks to a first version, typically
  • 3 months of fixes after launch in the build price
Get a written view in two working days

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.

  1. 01Week 1

    Week 1 baseline and risk list

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

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

  2. 02Weeks 2 to 3

    Pipeline and tests

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

  3. 03Weeks 3 to 5

    Environments and IaC

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

  4. 04Weeks 5 to 6

    Release lane and rollback

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

  5. 05Week 6

    Handover and training

    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.

Included to start: Audit, one pipeline for one app, staging and production, rollback. 3 to 5 weeks.

Pipeline platform
Environments
Hosting target
Add to the pipelinetap to add

Estimate only, excluding VAT

£7,500 to £14,500

This is an estimator, not a quote. Nothing is final until discovery sets your fixed price.

£9,000 to £17,500 with VAT at 20%

First pipelineLarger platform

3 to 6 weeks

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.

  • Social and creator apps

    Amara Social

    What we built

    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
    A workout post in Amara Social: a video, the title, muscle group tags, duration, number of exercises, level and a button to tick off exercises
  • Media and streaming

    Streaming service app: cloud hosting and video delivery

    What we built

    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
    A film page on a phone with the trailer, rating, running time, a play button for subscribers and an option to unlock the film with points

What clients say

  • React Native app development

    “Amara is built around creators, so posting had to be effortless: posts, short videos, Stories, recipes and workouts, with each creator deciding who sees what. AppAgentix built it for iPhone and Android from one codebase, and what I value most is the video: uploads process in the background, playback starts fast and holds up on mobile data. Moderation and audience controls were built properly, not as an afterthought. They worked like part of our team.”

    Clayton C.VP Engineering and AI, Amara
    Read the case study: Amara
  • Flutter app developmentMedia and entertainment

    “We wanted one streaming service that felt the same on phone, tablet and TV, whether people watch free with adverts, subscribe or rent a film. AppAgentix built the apps for iPhone, iPad, Android and Apple TV and the service behind them. They got the hard parts right: playback that starts quickly, a home screen that works with a TV remote, and billing that stays correct. The Android app has passed 50,000 downloads.”

    Michael S.CEO and Co-Founder, Play Now Media
    Read the case study: Play Now Media
  • Android app developmentHealthcare

    “Our patients needed the portal in their pocket: requesting visits, reading test results, reordering medicines and messaging their care team. AppAgentix built the Android app on our Epic MyChart system, careful where it matters: secure sign-in, no clinical detail on the lock screen, and patients choose what fitness data they share. The app has passed 50,000 downloads with 4.4 stars from over 750 reviews, and every release was tested before it reached our patients.”

    Tariq K.Associate Vice President, Epic Applications, UTHealth Houston
    Read the case study: UTHealth Houston

Not sure what your app would cost? Send us the idea and get scope, timeline and a price range in writing within two working days.

Ask what this would cost

Three ways to work with us

Pick by how much you can write down today. Prices in pounds, excluding VAT.

  • Fixed-price build

    Best whenYou can say what the product must do, and want one figure before work starts.

    Price

    • MVP from £15,000, 8 to 14 weeks
    • Two weeks of discovery first, its fee taken off the build price
    • Full iPhone and Android app in 4 to 8 months

    Terms

    • One fixed figure in writing after discovery
    • Fixes for 90 days after launch included
    • If we do not deliver what the written scope promises, we refund what you paid for the undelivered work within 7 days.

    You own the code, designs and accounts from the first commit.

    Start with discovery
  • Dedicated developers

    Best whenYou have a product lead and a backlog, and need more hands on it.

    Price

    • Engineer from £450 a day
    • Senior engineers and tech leads at higher day rates

    Terms

    • Billed monthly for the days worked
    • Three-month minimum, then 30 days’ notice
    • End within the first 10 working days with nothing owed
    • A replacement within 5 working days if someone is not the right fit

    The work passes to you as each monthly invoice is paid; accounts stay in your name.

    Hire app developers
  • Support plan

    Best whenThe product is live and must stay fast, secure and current with new phone and model releases.

    Price

    • From £750 a month
    • The first 90 days of fixes come with the build

    Terms

    • Three-month minimum, then 30 days’ notice
    • Security patches, compatibility checks and a monthly report

    Nothing moves to us: code, stores and cloud stay in your accounts.

    See support plans

Before the call: the one-page scope template

The ten questions discovery starts with: users, the jobs they need done, systems to connect, rules, deadline and budget. Fill it in, attach nothing else, and the first call starts at the right place.

Download the PDF

Technology we use for DevOps and CI/CD

Everything as code, releases on every merge, alerts with the cause.

  • Back end and AI services

    • Node.jsJavaScript runtime for scalable network applications
    • PythonLanguage for web development and scientific work
  • Databases and live data

    • PostgreSQLOpen-source database; pgvector adds vector search
    • RedisIn-memory store for caching and live messages
    • SupabasePostgres database with sign-in and file storage
    • FirebaseFirestore and Realtime Database: store and sync app data
  • Cloud and DevOps

    • DockerPackages and runs an app in a container
    • KubernetesRunning many services at scale
    • TerraformCloud set-up written as code, repeatable
    • AWSCloud hosting with a London region
  • Releases and monitoring

    • GitHub ActionsCI/CD platform to automate build, test and deployment
    • JenkinsOpen source automation server for CI and continuous delivery
    • SentryCaptures errors and alerts you with full context
    • DatadogPlatform for monitoring and security

DevOps and CI/CD implementation questions

Ask us at info@appagentix.co.uk

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

Most app projects run late. Let’s make yours the one that ships.

More than 95% of our projects are delivered on or before the agreed date. About 60% of our clients come back for a second project.

What happens next

  1. We reply within 30 minutesEvery day of the year. A developer at our app development company, not a sales team, reads your brief.
  2. A 30-minute callWe ask about users, deadlines and the systems you already run.
  3. A written view in two working daysScope, timeline and a price range, yours to keep.
Book a call

We reply from info@appagentix.co.uk. No mailing list.