Apex Fintech Solutions
Scaling Monorepo CI and Improving Delivery Reliability with Mergify
Apex Fintech Solutions
Location
Dallas, Texas, USA
Customer Since
March 2023
Team Size
350 engineers
Minh Tran
Platform Engineer
Apex Fintech Solutions is a cloud-native financial technology provider that enables hundreds of clients to launch, scale, and operate digital investing platforms for tens of millions of end investors. They offer clearing, custody, execution, and wealth-tech infrastructure, including ledger services, trade engines, and APIs.
Large monorepo with multi-language stack (Go, Java, Python, TypeScript) led to long build times and merge conflicts
CI latency and flaky tests created friction for developers working on critical SDK and API components
Manual merge coordination risked main branch instability and delayed releases
Apex Fintech operates a large monorepo supporting multiple languages and dozens of engineering teams. Before Mergify, developers manually managed merge timing to avoid breaking main or overloading shared CI resources.
With Mergify's Merge Queue, Apex introduced automated merge control and speculative branching. Every pull request is rebased on the latest main and tested before merge, ensuring reliability under load.
For Apex, Mergify’s Merge Queue became the cornerstone of their delivery process. With hundreds of engineers contributing to a single monorepo, managing merges manually had become impossible. The queue introduced structure, predictability, and confidence: every change now moves through the same clear path to production.
We use speculative branches to rebase on the latest main and test there, it helps catch issues early and keeps main green.
Minh Tran
Platform Engineer
The queue’s speculative testing ensures that every pull request is validated against the latest version of main before merging, catching potential conflicts early. This completely eliminated the "surprise breakages" that used to appear right after merges.
Apex migrated to Bazel to manage builds and tests across languages, reducing full CI runs from over two hours to about five minutes on average. By combining Bazel with Mergify's automation and merge queue, Apex ensures tests run only when PRs are ready and main remains stable.
The merge queue is a huge value from Mergify: it keeps our main stable and allows us to merge quickly with confidence. Priority queues and auto-reruns make the process smooth and predictable.
Minh Tran
Platform Engineer
Mergify's queue also helped Apex streamline cross-team collaboration. Multiple product lines, SDK updates, and infrastructure changes can all be implemented safely without conflicting with one another. Developers trust the process, and as a result, delivery velocity has increased across the board.
For Apex, Mergify's Merge Queue became the cornerstone of their delivery process. With hundreds of engineers contributing to a single monorepo, managing merges manually had become impossible. The queue introduced structure, predictability, and confidence: every change now moves through the same clear path to production.
