Skip to main content
    ProductsReign Factory

    Accelerate software delivery. Keep control of what ships.

    Reign Factory is designed to accelerate software delivery by adding implementation and test capacity. It works under a defined method and opens each change as a merge request in your repository. Source control, checks, approvals, pipelines and release remain with your team.

    Available · Beta Release Discuss your delivery priorities See the delivery path →

    Reign Factory is available in beta through a scoped engagement. Each engagement defines the work, operating boundary, required checks, person-involvement rules and measures before work begins.

    One item, end to end your path
    Reign Factory · operated for you by iTmethods Existing delivery controls One item from your backlog Eligibility the rules you set Isolated worker one item at a time Build and test Gateway on the path out A merge request in your repository Your checks your existing pipeline Review and approval your policy decides Merge and release your rules, your process A person is involved out of scope, a check unmet, or an item needing judgment — a named person reviews it and approves any next step You merge. Your pipeline releases.
    Everything to the right of the seam is the process you already run. Factory delivers the merge request, and your team takes it from there.
    Benefits

    What you gain.

    Reign Factory adds implementation and test capacity while each change stays inside the delivery controls your team already runs.

    Move more delivery work forward

    Factory adds implementation and test capacity for remediation, upgrades, migrations and selected roadmap work that is already understood but waiting for engineering time.

    Focus engineers on work that needs their judgment

    Factory performs implementation and test work while software engineers focus on product direction, architecture and complex delivery decisions.

    Keep delivery controlled and consistent

    Each change arrives as a merge request with its checks, results, findings and open issues attached. The customer's repository, pipeline, reviewers, approval policy, merge decision and release process determine what ships.

    In one month of our own engineering, 326 merge requests merged across eight repositories; the median time from merge-request open to merge was 19 hours. All 326 were recorded with an approval from a named iTmethods engineer. Read the population, period, exclusions and limitations.

    This is an internal sample from 11 July to 11 August 2026, measured in GitLab. It is a volume and cycle-time record for that population, not a customer result, success rate, benchmark or output multiple.

    The delivery path

    From a ticket to a merge request.

    You assign work to Reign Factory. It completes the implementation under a defined method and opens a merge request in your repository with its checks and findings attached. Your source control, reviewers, approvals, pipelines, merge and release process determine what ships. When an item needs a product, architecture or priority decision, Factory routes it to the person responsible.

    Reign Factory · operated for you by iTmethods
    Your software project · existing delivery controls
    Eligibility
    Agreed rules decide which work Factory takes on. Each decision shows the rule applied.
    Isolated worker
    Factory works on one item at a time.
    Reign Gateway
    Reign Gateway applies policy to each model call. Build and test run before Factory opens the merge request.
    Merge request
    Factory opens a merge request in your repository with its checks, findings and open issues attached.
    Your checks
    Your existing pipeline runs the checks configured for the project.
    Review and approval
    Reviewers examine the change, and your approval policy decides who authorizes it.
    Merge and release
    You decide whether to merge and when to release.
    Involves a person where judgment is needed Out of scope · check unmet · needs judgment
    A named person receives the item's current state and reason, reviews it and approves any next step.
    You set what it may work on The agreed rules define the repository, delivery path, change type and scope. Work enters the automated path only when it meets those rules, and each eligibility decision shows the rule applied.
    Every model call passes through Reign Gateway Gateway applies the agreed policy and records the caller, policy decision, destination, outcome, time and cost, subject to approved capture settings. A reviewer can trace that record to the item and its merge request.
    Everything lands in your repository Your repository holds the intended change, the checks that ran, the findings raised, open issues and the approval recorded against a named person, in one review path.
    A person stays in the path where review, approval or judgment is needed. Out-of-scope work, an unmet check or a decision needing judgment goes to a named person with the work's current state and reason. Autonomy is off by default and is turned on for an agreed population only with your written approval.

    Factory currently supports GitLab. GitHub and Bitbucket support is in development, as is Jira and Plane work intake. The engagement defines the response to a failed project check or scanner finding; the customer's pipeline, approval, merge and release controls remain decisive. Factory can work inside customer-operated tooling. Reign Ops is the separate route when iTmethods operates the engineering estate.

    The ask

    Discuss your delivery priorities.

    Let’s discuss one piece of work you want to advance.

    Discuss your delivery priorities