--- title: "Mergify Enterprise Server" description: "Run the Mergify merge queue on your own infrastructure, next to GitHub Enterprise Server or GitHub.com. Your code and data stay inside the environment you already secure." url: https://mergify.com/solutions/enterprise-server --- Mergify Enterprise Server # Mergify, inside your network. The full merge queue runs on your own infrastructure, next to your GitHub Enterprise Server. There is no new vendor cloud to authorize: it runs inside the boundary you already operate, and your security team reviews it like the rest of the software you run. [Talk to our team](https://mergify.com/discovery)[See how it fits your compliance boundary ↓](#regulated) mergify.yourcompany.internal Internal network Used by the platform teams that ship fast and keep CI green "Two-step CI completely transformed how we handle long hardware tests. Instead of burning hours on repeated runs, we validate once and merge with confidence." Rushin Shah, Sr. Manager DevInfra · Cerebras "The merge queue is a huge value from Mergify: it keeps our main stable and allows us to merge quickly with confidence." Minh Tran, Platform Engineer · Apex Fintech Solutions "You get the benefits of Mergify immediately. There is no competitor doing stuff like this." Florian Berchtold, Software Engineer · Luminar "The merge queue is a time-saver! Contributors no longer have to carry the mental load of monitoring their PRs!" Johan Lorenzo, Staff Release Engineer · Mozilla "We transitioned from manual chaos to over 20 safe deploys per day. Mergify is becoming a critical part of our delivery function." Chris Irving, Engineering Manager · Jane "Our merge queue is like a safety net. Every PR that lands has been tested, approved, and verified under the exact same conditions." Fabien Marty, Senior Staff Software Engineer · Botify "With dozens of engineers and long-running CI jobs, Mergify turned what used to be a daily bottleneck into a background process. Our teams focus on hardware, not merge logistics." Ben Holtzman, Senior Design Enablement Engineer · AheadComputing "Before Mergify, we spent too much time manually coordinating merges. Now everything flows automatically." Nicolas Beaussart-Hatchuel, Senior Staff Software Engineer · PayFit "Mergify was the best fit. It saved a couple of hours per engineer per month and resolved our bottleneck with the merge queue." Tomas Nekolny, Engineering Manager · Productboard "The support on Slack is really good, reactive and transparent. We have other partners where problems feel less transparent. With Mergify, it's fluid." Clément Danjou, VP Blockchain · Zama Regulated environments ## A merge queue that fits inside your compliance boundary Teams under FedRAMP, ITAR, CMMC or internal data rules often cannot send code to a vendor's cloud. Mergify Enterprise Server runs where your GitHub already runs, behind the controls you already have. Your network GitHub Enterprise Server Mergify Enterprise Server Your CI runners Data stored in databases you own ### Your compliance scope stays yours Security teams review Mergify Enterprise Server like the rest of the software they already run. There is no new vendor cloud to assess. [Talk to our team](https://mergify.com/discovery) #### Inside your authorization boundary Mergify runs in the environment you already secure and certify. You deploy and operate it, and nothing Mergify hosts sees your code. #### Your data stays yours Pull requests, queue history and CI results live in systems you own, back up and audit. #### Your upgrade calendar You install a new version when it suits you, so an upgrade never lands in the middle of a release freeze. Made to run in Systems under a FedRAMP authorization · ITAR programs · CUI and CMMC · Sovereign and private clouds · On-premise data centers For teams in Defense and aerospace · Government and public sector · Financial services · Healthcare and life sciences · Semiconductors and hardware · Automotive Change management ## Evidence for every merge Auditors ask the same questions about every change that reaches production. Mergify records the answers as part of merging, so nobody has to rebuild them later. ### Who approved this change? Queue rules can require approvals from named reviewers or teams before a pull request is allowed to merge, and GitHub already blocks authors from approving their own work. NIST 800-171 03.01.04NIST 800-53 AC-5PCI DSS 6.2.3.1SOX ITGC ### Was it tested against what main really looks like? The merge queue tests every pull request on top of the latest main and the changes queued ahead of it, and merges only when the required checks pass on that exact result. NIST 800-171 03.04.03NIST 800-53 CM-3PCI DSS 6.5.1SOC 2 CC8.1DORA Art. 9(4)(e) ### Which rule let it through, and did anyone step around it? Each queue decision names the rule that applied. Freezes, pauses and manual queue commands are recorded with the person who triggered them. NIST 800-171 03.04.03NIST 800-53 CM-5PCI DSS 6.5.4SOX ITGC ### Can we see what happened to every change? The event log records each queue event with the checks, conditions and commit involved, and your audit tooling can read it through the API. Export it to the audit store you already keep, for as long as your rules require. NIST 800-171 03.03.01NIST 800-53 AU-221 CFR 11.10(e)HIPAA 164.312(b) The control references show where Mergify's records fit your evidence. They are mappings, not certifications: compliance remains a property of your system and your processes. [How the merge queue works](https://mergify.com/product/merge-queue). ## Same Mergify, your choice of where it runs Mergify Cloud is the fastest way to start. Enterprise Server is for teams whose code has to stay in their own network. Mergify Cloud We run it for you Enterprise Server You run it, anywhere Merge Queue ✓ ✓ CI Insights ✓ ✓ Test Engine ✓ ✓ GitHub.com ✓ ✓ GitHub Enterprise Server ✓ Where it runs Mergify's cloud Your infrastructure Who operates it Mergify Your team, with our support > Mergify finally gave us a merge queue that behaves predictably under heavy load. With limited hardware capacity and multi-hour tests, reliability is everything, and Mergify made stability a solved problem for us. Rushin Shah Sr. Manager, DevInfra and Automation Architect at Cerebras ## From security review to purchase order 1. 01 ### Security review Send us your questionnaire. Your team reviews Mergify like any other software you run in-house. 2. 02 ### Evaluate on your infrastructure We set up an evaluation in your environment, with an engineer to help with the first deployment. 3. 03 ### Purchase your way An annual license, bought by purchase order through your normal procurement process. ## FAQ ### Can I self-host Mergify? Yes. Mergify Enterprise Server is the on-premise edition of Mergify. It runs on your own infrastructure and connects to GitHub Enterprise Server 3.14 or newer, or to GitHub.com. ### Is Mergify FedRAMP authorized? No. Mergify Cloud is not FedRAMP authorized. FedRAMP covers cloud services, and Mergify Enterprise Server is software you deploy and operate in your own environment, so it falls under your own authorization to operate, like the rest of the software you run. No Mergify-hosted service sits in the path of your code. ### Can we use Mergify on ITAR, CUI or CMMC programs? Mergify Enterprise Server keeps your code and data inside the environment you control, so it can be deployed within the systems those programs already cover. Your security team decides where it runs and who can reach it. ### Does Mergify make us compliant? No tool does that on its own. Mergify supports the evidence your auditors ask for on every merge: approvals, testing before merge, the rule that applied and a record of each queue event. Compliance stays a property of your system and your processes. ### What does it run on? Mergify ships as a container image. It runs on Kubernetes or virtual machines, in your cloud account or your own data center. ### Do we get every Mergify product? Yes. Enterprise Server includes Merge Queue, CI Insights and Test Engine. ### Can we evaluate it before buying? Yes. Tell us about your environment and we set up an evaluation on your own infrastructure, with an engineer to help with the first deployment. ### Can we buy through our procurement process? Yes. Enterprise Server is sold as an annual license, bought by purchase order through your normal procurement process. ### How is it priced? Enterprise Server is part of the Enterprise plan and is licensed per seat, per year. [Talk to us](https://mergify.com/discovery) for a quote. ## Run Mergify on your GitHub Enterprise Server. Tell us about your environment and we'll set up an evaluation on your own infrastructure. [Talk to our team](https://mergify.com/discovery)[See pricing](https://mergify.com/pricing)