Skip to Content

Feature Availability Matrix

Use this matrix to understand where a feature appears and whether it depends on plan, workspace setup, or MergeLoom support enablement.

FeatureCloud HostedSelf HostedNotes
Ticket intakeYesYesController-managed polling and manual sync.
GitHub PR outputYesYesGitHub.com is the public documented path.
GitLab MR outputYesYesSelf-managed GitLab requires matching base/API URLs.
Azure Repos PR outputYesYesAzure DevOps Services-oriented public path.
Cloud RuntimeYesNoCloud-only controller page.
Local Worker UINo customer accessYesSelf Hosted gateway UI.
Provider setupMergeLoom-managedCustomer-managedSelf Hosted supports CLI/API/BYO provider paths.
Run creditsYesYesBilling behavior can depend on plan and recovery path.
Cloud AI creditsYesUsually noSelf Hosted provider spend is usually paid to the customer’s provider.
Ticket AuditControllerLocal Worker UICloud evidence is surfaced through controller audit pages.
Code AuditController, plan-gatedLocal Worker UI, plan-gatedExport availability can be plan-gated.
Context EngineWhere enabledWhere enabledAvailability and capacity depend on workspace setup and plan.
CampaignsPlan-gatedPlan-gatedJira Epic campaigns are feature-gated.
Review notificationsPlan-gatedPlan-gatedSlack/Teams incoming webhooks.
OIDC SSOYesYesConfigured in Controller UI Account & Access.
Worker app-native SSONot applicableNoProtect Local Worker UI with private network controls.

Confirm these items before a production rollout:

  • Context Engine availability and capacity for your workspace
  • Cloud Hosted model aliases available on your plan
  • cloud audit retention and export availability for your plan
  • GitHub Enterprise or Azure DevOps Server requirements, if applicable
  • whether OIDC covers your SSO requirements
  • Self Hosted audit retention settings

Related page: FAQ.