Making Qovery builds as fast as GitHub Actions, and then faster

Qovery reports that its container builds were previously 1.4 to 3.6 times slower than GitHub Actions in a public September benchmark, largely because of fixed infrastructure overhead rather than application build work. October changes—including doubling builder memory to 16 GB, adopting local NVMe storage, using zstd compression for images and caches, and checking for existing images before cloning repositories—reduced median customer build times from about 4.5 to 2.5 minutes. The company also identified a BuildKit readiness-check issue that added roughly 26 seconds to every build; after adopting Docker Buildx v0.39, Qovery estimates performance matches GitHub Actions for typical Python and React projects and is 12% to 16% faster for heavier Next.js, PHP, and large-image workloads, while still trailing on very small builds. New deployment logs expose timing by build step, and an AI-powered Build Optimizer analyzes Dockerfiles, logs, and cache history to recommend changes without applying them automatically. Qovery plans further improvements through reusable images across environments, faster CPUs, local persistent caches, asynchronous cache exports, faster repository and base-image retrieval, and reduced setup overhead, with the broader goal of measuring performance from commit to running code rather than only to image publication.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.