# The Night We Moved Our CI

DevFeed: [The Night We Moved Our CI](<https://devfeed.tech/articles/the-night-we-moved-our-ci-5822.md>)

Original publisher: [Read original article](<https://neon.com/blog/the-night-we-moved-our-ci>)

Author: Fedor Dikarev

Published: 2025-10-31T16:32:42Z

Content type: article

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [ci](<https://devfeed.tech/topics/ci.md>), [migration](<https://devfeed.tech/topics/migration.md>)

Tags: [amd](<https://devfeed.tech/tags/amd.md>), [aws](<https://devfeed.tech/tags/aws.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [compute](<https://devfeed.tech/tags/compute.md>), [cost](<https://devfeed.tech/tags/cost.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [migration](<https://devfeed.tech/tags/migration.md>)

## AI overview

A developer team describes how a rushed CI migration from Hetzner bare metal to AWS caused startup delays, cold caches, stricter compliance requirements, and sharply higher costs. The expanded CI scope also added ARM builds, re-enabled tests, and cloud E2E checks for pull requests.

## Source excerpt

Once upon a pipeline... It was a nice summer evening, and our CI lived happily in a familiar castle: Hetzner. Bare-metal towers gave us everything we needed, with cheap CPU and RAM per unit, free internal traffic, and huge local disks to hoard caches like dragons guard gold. Our wo...