Cloud Hosted Execution

Cloud Hosted is the fastest way to run MergeLoom. MergeLoom operates the worker runtime, calls the approved cloud AI provider path, and shows run visibility inside the customer controller.

Use Cloud Hosted when you want ticket-to-code automation without installing a worker in your own infrastructure.

This Is in the Customer Controller

Configure Cloud Hosted execution from https://controller.mergeloom.ai. Cloud customers do not use the local worker UI at http://127.0.0.1:8010/.

What MergeLoom Runs for You

For Cloud Hosted workspaces, MergeLoom provisions and operates the managed execution path:

a cloud worker gateway for the workspace
worker executor capacity controlled by the plan
cloud provider routing
live run state in the controller
cloud ticket audit and cloud code audit views

Each customer cloud runtime is separated at the platform layer. You still keep your normal work tracker, code host, labels, statuses, comments, and review process.

Cloud Account Requirements

Cloud Hosted free workspaces require:

verified email
a verified payment card through Stripe setup mode
connected work tracker
connected code host
configured workflow intake
at least one enabled repository in the repository catalog

The card check is used for cloud abuse prevention and usage beyond free allowances. The free plan can still start without a paid subscription.

Self Hosted workspaces do not need the cloud payment card gate because the customer operates the worker and provider path.

AI Credits and Model Access

Cloud Hosted plans use MergeLoom AI credits. The customer controller shows the current credit balance, plan state, and cloud billing state. Some prepaid balances do not renew automatically.

Model access is controlled by plan. Free plans can be restricted to a lower-cost default model. Paid cloud plans can expose a wider model list and let the workspace select a default model.

The Cloud Runtime page shows:

current default model
allowed model aliases for ticket-level overrides
live run status
provider readiness
email and card verification state

Ticket-Level Model Overrides

When the plan allows more than one model, MergeLoom can expose model aliases that operators can use on tickets.

Example model label, where your workspace exposes model labels:

model:sonnet

Use the alias list shown in the Cloud Runtime page. Free workspaces may only have one allowed model. The code-confirmed standalone form is a label, not an arbitrary ticket comment.

If your workflow uses ticket directives in the ticket description, put provider or model overrides inside a [JCA]...[/JCA] block:

[JCA]
model=sonnet
[/JCA]

Description-level directives take precedence over model labels.

Where to Watch Cloud Runs

Cloud runs are watched from the customer controller:

Dashboard for workspace status and metrics
Cloud Runtime for the current live execution
Audit for ticket audit, code audit, and controller audit tabs
Billing for AI credit balance and plan state

For more detail, see Cloud audit and Code audit.

When to Choose Self Hosted Instead

Choose Self Hosted if your team needs:

repository checkout inside your own infrastructure
model calls from your own network boundary
worker-local provider credentials
worker-local deep traces and code audit storage
private provider endpoints or a bring-your-own-provider model

See Self Hosted worker execution for that path.