Skip to content
Services

DevOps as a Service

Set up how your software is built, released and watched, then hand it to your team or run it for you.

  • Named engineers

    You know who looks after your systems.

  • Fixed monthly price

    Cancel with one month of notice.

  • You own everything

    Code, accounts and documentation stay with you.

What we set up

Six jobs, done properly

  • Build and release pipelines

    Every change is built, tested and released the same way. Rolling back a bad release takes one step.

    CI and CD
  • Infrastructure as code

    Your servers, networks and databases are described in files kept in version control, so they can be reviewed and rebuilt.

    Code, not clicks
  • Separate environments

    Development, testing and live are built from the same code, so what you test is what you ship.

    Dev, test, live
  • Monitoring and alerts

    Dashboards for the things that matter, and alerts that reach the right person. Every alert comes with a note on what to do about it.

    Watch
  • Security basics

    Secrets kept out of code, access by role, dependency checks on every build, and backups that we have actually restored.

    Protect
  • Cloud cost

    A monthly look at what you pay for and what you do not use, with the savings we find put into effect.

    Spend
How it runs

A typical first three months

  1. Weeks 1 to 2

    Review

    Review of code layout, pipelines, hosting and bills, plus conversations with the people who release software today. Output: a short list of changes in order of value.

  2. Weeks 3 to 6

    Pipelines and environments

    The automated release path is built first, because it removes the most risk. Your engineers use it from the first week it exists.

  3. Weeks 7 to 10

    Infrastructure and monitoring

    Infrastructure is moved into code and monitoring and alerting are put in place. A rollback and a restore are then tested on purpose.

  4. Week 11 on

    Run or hand over

    Your team takes it on with training and written runbooks, or it is run for you each month with reports on cost and reliability.

Who it suits

Three situations we see most

  • Nobody owns it

    Developers do operations on the side, and it only gets attention when something breaks.

  • One person holds it together

    Releases and fixes depend on someone who cannot take a holiday.

  • The bill keeps growing

    Cloud costs go up each month and nobody can say which part of it is needed.

Why us

We build it and we run it

We operate software for a living, so we design for the 3am problem as well as the demo.

  • Named engineers

    You know who is looking after your systems and how to reach them.

  • Everything is written down

    Setup, runbooks and decisions are documented, so anyone can pick them up.

  • You can leave

    Accounts, code and documentation stay with you, so ending the service loses you nothing.

Example prices

What it costs

Please noteThese are example prices, to show roughly what this service costs. What you pay depends on the size of your business, how many teams are involved and the level of service you need. We confirm a fixed price in writing before any work starts.

  • Review

    We look at how you build, ship and run software, and what it costs.

    From £3,000fixed price, two weeks

    Contact us
    • A review of your pipelines and environments
    • A breakdown of your cloud spend
    • A short list of changes in order of value
  • Recommended

    Platform build

    We set up the pipelines and infrastructure your engineers need.

    From £15,000per project, scoped up front

    Contact us
    • Everything in Review
    • Automated build, test and release
    • Infrastructure written as code
    • Handover and training for your team
  • Managed

    We run it for you and keep the bill under control.

    From £4,500per month

    Contact us
    • Everything in Platform build
    • Monitoring and on-call cover
    • Monthly cost report with savings actioned
    • Cancel with one month notice
Questions

Questions about this service

Do we need to move to a new cloud provider?

No. We work with the provider you use, whether that is AWS, Azure, Google Cloud or something else.

Can our own engineers work with yours?

Yes, and we prefer it. We document as we go so your team can take over any part of it.

What happens at 3am if something breaks?

On the Managed plan, our engineers are on call and respond under the terms we agree in writing.

Can we stop the monthly service?

Yes. You give one month of notice and there is no minimum term.

Still have a question?

Tell us what you are trying to do. We reply within one working day.

Contact us

Tell us what you run

Describe your setup in a few lines and receive a recommendation on where to start.