Skip to main content
    DARK FACTORY · PILOT · 2026 COHORT

    Agents build it. Humans approve it. Reign proves it.

    A ninety-day, governed pilot on one real software-delivery workflow. Your coding agents, your repo, your existing toolchain, run inside Dark Factory and governed end to end by Reign. Audit-grade evidence from the first governed action.

    A selective 2026 cohort for regulated institutions, by application. Every pilot is led by a named principal engineer, so intake is deliberately limited.

    Schedule an executive briefingApply for the pilot
    Or book a scoping call directly
    Engagement
    Ninety days from kickoff
    Deployment
    Your VPC, on-prem, or air-gapped
    Aligned with
    OSFI E-23 · EU AI Act · ISO 42001 · NIST AI RMF · FINOS AIGF
    Intake
    2026 cohort, by application
    What the pilot proves

    The pilot proves four things, in order.

    1. Dark Factory can run a governed, end-to-end SDLC on one real workflow.

      A ticket is picked up, code is written and tested, a merge request opens, and the human approval gate holds, every time, on your own repository.

    2. Reign can produce tamper-evident, examiner-ready evidence as a byproduct of the factory’s runtime.

      Not a separate reporting exercise bolted on afterward. The evidence is a byproduct of the factory running, sealed as work happens.

    3. The human approval gate holds without materially slowing the team down.

      Evidenced by cycle-time and merge-rate data captured from your own environment, not a vendor benchmark.

    4. Executives get visibility into what agents built, what was blocked or escalated, and what a human approved.

      Rolled up into a risk posture your CISO, CRO, or Chief Audit Executive can read directly.

    How it runs

    Six steps. Ninety days.

    The pilot scope is deliberately narrow so the work is real. Pick the repository or service line with the coding-agent activity your CISO or engineering leadership is most eager to govern. Instrument it end to end. Walk away with audit-grade evidence and a plan for the rest of the SDLC estate.

    1. Scope.

      Select one repository or service line and the coding agent(s) already in use or under evaluation (Cursor, Claude Code, Copilot, Codex, Devin, Factory, or others).

    2. Integrate.

      Wire Dark Factory to the tracker, source control, CI/CD, and security scanning you already run. No toolchain replacement required.

    3. Authorize.

      Define the human approval policy and the runtime policy for sensitive actions before any agent runs against production-bound work.

    4. Run.

      Agents pick up tickets, write and test code, and open merge requests inside isolated sandboxes.

    5. Evidence.

      Every action, from ticket claim to merge, is sealed to Reign’s tamper-evident ledger, examiner-ready on demand.

    6. Expand.

      Move to the next repository, service, or workflow with the governance model already proven inside your environment.

    What we ask of you
    • Executive sponsorship and decision-maker access across engineering, security, and risk or compliance.
    • One coding agent, one repository or service line, already in production or about to be.
    • A regulator or audit surface that gives the ninety-day scope its forcing function (OSFI E-23, EU AI Act, SOC 2, an internal audit cycle, or equivalent).
    • Capacity to host Dark Factory and Reign in your VPC, on-prem, or fully air-gapped environment. iTmethods does not custody your code, your models, or your data.
    • Engineering and security workshop time during the ninety days.

    The pilot is delivered by a named principal engineer and a small pod from the Forge and Reign practices, sized to the engagement. Same face from scoping call to day ninety. There is no platform cost during the ninety-day pilot. The engagement converts to an annual Forge / Dark Factory platform license on cohort close, on terms documented in the engagement charter from day one.

    Questions

    Before you apply.

    Is there a cost during the Dark Factory pilot?

    No. There is no platform cost during the ninety-day pilot. The engagement converts to an annual Forge / Dark Factory platform license at cohort close, on terms documented in the engagement charter from day one.

    How quickly will I hear back after applying?

    First response within five business days. A scoping call is scheduled within two weeks of the application if there is mutual fit.

    What happens after the pilot ends?

    The pilot converts to a standard annual Forge / Dark Factory license, scoped to your deployment model (SaaS, your own cloud, or air-gapped) and the volume of governed work it runs, at the rate set in your engagement charter.