---
company: "AheadComputing"
title: "Optimizing Hardware CI Efficiency and Visibility with Mergify"
engineers: "100 engineers"
industry: "Semiconductor"
companyType: "Enterprise & HW"
description: "AheadComputing designs breakthrough 64-bit RISC-V application processors, targeting next-generation workloads across AI, cloud, and edge devices."
location: "Portland, Oregon, USA"
companyUrl: "https://www.aheadcomputing.com/"
companyUrlDisplay: "aheadcomputing.com"
customerSince: "2025-04-11"
logo: ../../assets/customers/aheadcomputing-logo.png
screenshot: ../../assets/customers/aheadcomputing-screenshot.png
video: null
stakeholders:
  - name: "Ben Holtzman"
    avatar: ../../assets/customers/aheadcomputing-avatar.jpeg
    role: "Senior Design Enablement Engineer"
result: "40% faster CI runs and fewer flaky failures"
highlight: "40% faster CI runs, fewer flaky failures"
replaced: "GitHub's merge queue"
challenges:
  - "Complex hardware CI pipelines with long-running tests (up to 90 minutes) slowed down development feedback loops."
  - "GitHub's native merge queue couldn't handle Ahead's advanced requirements — freezes, prioritization, and custom rules."
  - "Lack of CI observability made it hard to identify wasted compute and flaky test behavior."
products:
  - "Merge Queue"
  - "CI Insights"
  - "Test Engine"
testimonials:
  - "With Mergify, we can finally run our merge queues the way we want: custom rules, multiple queues, and fine-grained control over every condition."
  - "Mergify gives us the control and visibility we never had with GitHub's queue. It's become our CI command center."
contentSection1: |
  <p>AheadComputing is building a next-generation <strong>RISC-V CPU core</strong>, created by a team of former Intel engineers with deep experience in high-performance compute. As the company grew, its CI system became a bottleneck.</p><p>"Hardware CI is a different world," explains <strong>Ben Holtzman</strong>, Infrastructure Engineer. "Tests can run for 90 minutes, and you can't afford false failures or mismanaged queues.”</p><p>When Ahead first adopted GitHub's native merge queue, they quickly encountered scaling limits: a lack of control over scheduling, prioritization, and fine-grained role conditions. "We needed something programmable that could adapt to how we actually work," says Holtzman.</p>
contentSection2: |
  <p>Ahead Computing fully migrated to <strong>Mergify's Merge Queue</strong>, using advanced scheduling and conditions to ensure reliable merges across multiple hardware and software workflows.</p><p>By combining <strong>scheduled freezes</strong>, <strong>multi-queue setups</strong>, and <strong>dynamic labeling</strong>, the team can manage merges for long-running tests without risking broken main branches or wasted compute.</p><p>They also implemented <strong>Mergify's CI Insights</strong>, gaining full visibility into runtime performance, skipped jobs, and resource usage across their monorepo.</p>
contentSection3: |
  <p>AheadComputing’s next step is to integrate flaky-test detection and automatic retries for self-hosted runners. “Our hardware tests are unique,” says Holtzman. “If we can automatically detect and retry flaky runs, that’s a massive time saver.”</p><p>By pairing Mergify’s Merge Queue with CI Insights, AheadComputing is creating a continuous integration system that scales with the complexity of hardware — without slowing engineers down.</p>
---
