Cloud vs Self Hosted Connectors
Cloud Hosted and Self Hosted use the same Controller UI integration records. The difference is where code execution happens after the controller creates a job.
Same in Both Modes
Section titled “Same in Both Modes”The customer controller owns:
- work tracker OAuth or app connections
- code host OAuth or app connections
- repository catalog sync
- workflow intake settings
- repository routing labels
- Confluence/context source configuration
- Slack and Teams review notification webhooks
- PR/MR coordination after worker execution
Self Hosted workers do not store Jira, GitHub, GitLab, Azure, monday.dev, Linear, or Confluence workspace connection setup as their primary configuration. They receive job-scoped access details when they start work.
Cloud Hosted
Section titled “Cloud Hosted”In Cloud Hosted mode:
- MergeLoom operates the worker runtime
- the managed cloud worker receives job-scoped repository access
- Cloud Runtime and Cloud Audit appear in the controller
- provider access is managed by MergeLoom according to the plan
Self Hosted
Section titled “Self Hosted”In Self Hosted mode:
- your worker gateway and executors run the code path
- provider credentials are local to the worker or provisioned through your deployment
- the worker receives job-scoped repository access from the controller
- Ticket Audit and Code Audit live in the Local Worker UI
Connector Support Notes
Section titled “Connector Support Notes”- Jira and Confluence paths are Atlassian Cloud-oriented in these docs.
- GitHub docs describe GitHub.com. Contact MergeLoom support before planning GitHub Enterprise.
- GitLab.com and self-managed GitLab are supported through matching base and API URLs.
- Azure docs are Azure DevOps Services-oriented. Contact MergeLoom support before planning Azure DevOps Server.
- monday.dev uses monday.com OAuth.
- Linear uses OAuth with read/write scope.
Related page: OAuth Callbacks and Scopes.