MergeLoom

Run MergeLoom Inside Your Own Infrastructure

Self Hosted keeps checkout, Context Engine assembly, provider calls, validation, traces, and PR/MR prep inside your boundary while MergeLoom still coordinates the workflow.

Your team controls the worker, AI provider path, secrets, commands, and local evidence. MergeLoom keeps the ticket-to-PR loop moving.

Customer WorkerProvider ChoiceLocal ValidationWorker AuditSecrets ControlPR/MR Handoff
Boundary Map
Product Map
  1. Step 01
    Controller Coordinates
  2. Step 02
    Worker Checks Out Code
  3. Step 03
    Provider Runs In Boundary
  4. Step 04
    PR/MR Returned

Keep Sensitive Execution Where It Belongs

Some repositories, credentials, test environments, and provider paths cannot leave your perimeter. Self Hosted keeps the sensitive work inside your controls.

Code Checkout

Repository access happens on the worker your team operates.

Provider Credentials

CLI login, API keys, and cloud identity stay in your environment.

Local Validation

Tests run where private packages, networks, and secrets already exist.

Local Audit Evidence

Deep traces and Code Audit evidence stay on the worker path.

Your Infrastructure Does The Work

The controller coordinates intake and handoff. Your worker handles the code-facing work, provider calls, validation commands, and local evidence.

  1. STEP 01

    Enroll The Worker

    The controller provides tenant values and enrollment tokens for the worker install.

  2. STEP 02

    Run Gateway And Executor

    Docker Compose or Helm starts the worker components inside your environment.

  3. STEP 03

    Choose Your Provider

    Use approved CLI agents, private endpoints, Vertex AI, AWS Bedrock, or Azure Foundry.

  4. STEP 04

    Execute Locally

    The worker checks out code, assembles context, calls the provider, runs validation, and prepares branches.

  5. STEP 05

    Return The PR/MR

    The review request returns to GitHub, GitLab, or Azure Repos.

  6. STEP 06

    Keep Local Evidence

    Ticket Audit, Code Audit, deep traces, and local run state live on the worker side.

Full Control Without Losing The Workflow

Self Hosted lets security and platform teams choose where code, credentials, provider calls, validation, and deep traces live.

Controller And Worker Split

The controller coordinates intake and routing. The worker owns code-facing execution.

Provider Flexibility

Use approved CLI agents, OpenAI-compatible endpoints with tool calling, or cloud AI platforms.

Secrets Stay Yours

Use platform-managed secrets, workload identity, or worker-side provider setup.

Local Evidence Ownership

Deep run traces and Code Audit evidence stay worker-owned instead of centralized in the cloud controller.

Cloud Hosted

  • Fastest Path For Managed Workers
  • Cloud Audit Lives In The Customer Controller
  • Provider Path Is Managed Through MergeLoom Today

Self Hosted

  • Sensitive Execution Stays In Your Environment
  • Worker-Local Audit Supports Security Review
  • Provider Path Follows Your Infrastructure Controls

See Runs Where They Actually Happen

Track worker readiness, live execution, latest run results, and audit history inside the environment where the work runs.

MergeLoom Self Hosted runtime home showing worker identity, current execution state, and latest run result.
Runtime home showing worker readiness, current execution, and latest run status.
MergeLoom Self Hosted ticket audit showing retained run history, worker status, and audit evidence.
Ticket audit showing retained run history, worker status, and execution evidence.

Your Code. Your Runtime. Your Rules.

Self Hosted makes the boundary clear: your worker handles sensitive execution while the controller keeps the workflow moving.

  • Worker-Owned Execution

    Checkout, context assembly, provider calls, validation, repair, and branch prep happen on the worker.

  • Controller Coordination

    The controller handles intake, routing, queue state, integration state, and PR/MR metadata.

  • Allowed Commands

    Operators define which commands the worker runs during validation.

  • Backup Responsibility

    Back up the worker data volume when worker-local Code Audit evidence must survive host replacement.

Use Self Hosted When Control Matters More Than Speed

Choose Self Hosted when security, network, provider, or compliance requirements make customer-operated execution the right path.

Regulated Repositories

Keep sensitive checkout and traces inside customer infrastructure.

Private Providers

Use approved provider paths, private endpoints, or cloud workload identity.

Local Dependencies

Run validation where private packages, services, and secrets already exist.

Platform-Controlled Secrets

Use Kubernetes Secrets, Docker secrets, or workload identity instead of vendor-held keys.

Deep Audit Ownership

Keep execution detail and Code Audit evidence on the worker side.

Long-Term Operations

Operate the worker as part of your normal platform runtime.

Self Hosted FAQ

What Stays On The Worker?

Checkout, context assembly, provider calls, validation, repair attempts, branch preparation, worker-local traces, Ticket Audit, and Code Audit.

What Does The Controller Still Do?

The controller coordinates intake, routing, queue state, integration setup, and PR/MR workflow metadata.

Which Providers Does Self Hosted Use?

Supported paths include Codex CLI, Claude Code CLI, OpenAI-compatible tool-calling endpoints, Vertex AI, AWS Bedrock, and Azure Foundry.

Is Self Hosted Always Better Than Cloud Hosted?

No. Cloud Hosted is faster to start. Self Hosted is better when runtime boundary, provider control, and local evidence ownership matter.

Explore Related Product Areas

Start Free With No Risk

Pay For Outcomes, Not Seats

Run MergeLoom on scoped work before rolling it out. You only pay when a run opens a PR/MR for review, not for seats or tickets that stop before handoff.

Cloud

50 Free PR/MR Runs

Then From £4 Per PR/MR

Self Hosted

50 Free PR/MR Runs

Then From £2 Per PR/MR

Paid Outcomes

Only PR/MR Runs Count

No PR/MR, No Run Charge

Start Free Request A Free Demo
  • Free To Start
  • Pay For Outcomes
  • No Lock-In Contracts
  • No Credit Card Required (Self-Hosted)
  • Cancel Anytime

No PR/MR, No Run Charge · No Seat Pricing · Human Review Stays In Control

See Pricing