No Worker Install
Skip runtime setup until the team has proven the workflow with real PR/MR output.
Cloud Hosted is the fastest way to prove MergeLoom. Connect your tools, route approved tickets, and get validated PRs/MRs back without installing worker infrastructure.
You still get context, validation, audit trails, cost visibility, and human review. We handle the runtime.
Some teams need proof before platform work. Cloud Hosted lets you start with real tickets while MergeLoom handles the execution layer.
Skip runtime setup until the team has proven the workflow with real PR/MR output.
Cloud Hosted uses Anthropic through MergeLoom today, with credits handled in the product plan.
Connect tools, set workflow rules, and start with scoped tickets quickly.
The output still lands as a PR/MR for normal engineering review.
Cloud Hosted changes who runs the worker, not how your team reviews code. MergeLoom handles execution while your engineers keep approval control.
Link work trackers, repository access, and workflow rules in the controller.
The hosted path checks out code, adds Context Engine evidence, runs the agent, and prepares output.
Cloud runs use Anthropic through MergeLoom today, with credits handled through workspace billing.
Quality Agents and configured checks run before the PR/MR reaches engineers.
Token usage, cost estimates, duration, audit evidence, and outcomes stay visible in the controller.
MergeLoom opens the review request. Your team approves, merges, and releases.
Cloud Hosted removes infrastructure setup while keeping the controls engineering teams need: context, validation, telemetry, audit trails, and PR/MR handoff.
Teams avoid worker enrollment, updates, and execution environment maintenance.
Use credits through MergeLoom instead of setting up a separate provider account for the first rollout.
Ticket Audit, Code Audit, and Controller Audit stay visible for Cloud Hosted runs.
Cloud execution still returns code to GitHub, GitLab, or Azure Repos for review.
Cloud Hosted gives teams live run state, validation evidence, and audit history without a local worker UI.
Fast rollout still needs clear boundaries for execution data, provider path, security review, and merge control.
Temporary execution data is deleted after the run. Logs, prompts, traces, and audit records follow workspace settings.
Cloud Hosted uses Anthropic through MergeLoom today.
Procurement teams get current security documentation during review.
Cloud Hosted prepares review output. Humans stay in the merge path.
Cloud Hosted is strongest when the team wants real PR/MR output before owning worker infrastructure.
Prove the workflow before assigning platform ownership.
Avoid worker operations when the team needs delivery capacity quickly.
Use plan credits and Anthropic through MergeLoom today.
Keep run evidence, token usage, cost estimates, and outcomes in the controller.
Continue reviewing through GitHub, GitLab, or Azure Repos.
Move to Self Hosted later if runtime boundary requirements change.
No. Cloud Hosted runs on MergeLoom-managed execution, so there is no Docker Compose, Helm, or worker enrollment to handle.
Cloud Hosted uses Anthropic through MergeLoom today, with AI credits handled through MergeLoom plans.
No. It opens a PR/MR for human review in the connected code host.
Choose Self Hosted when checkout, provider calls, validation, or deep traces need to stay inside your own infrastructure boundary.
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
Then From £4 Per PR/MR
Self Hosted
Then From £2 Per PR/MR
Paid Outcomes
No PR/MR, No Run Charge
No PR/MR, No Run Charge · No Seat Pricing · Human Review Stays In Control