> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-dxp/licensing-and-dependencies/commercial-product-dependencies.md).

# Commercial Products, Relations, and Dependencies

Describes the Umbraco commercial products, their dependencies and relations.

The following diagram shows the Umbraco commercial products, their dependencies, and the relations between them. Depending on your setup, you may need one or more of the additional packages shown here when working with them.

```mermaid
graph RL
    subgraph Core
        CMS["Umbraco.CMS"]
        Licenses["Umbraco.Licenses"]
        Licenses --> CMS
    end

    subgraph "Commercial Products"
        Deploy["Umbraco.Deploy"]
        Forms["Umbraco.Forms"]
        Engage["Umbraco.Engage"]
        Commerce["Umbraco.Commerce"]
        Workflow["Umbraco.Workflow"]
        UIBuilder["Umbraco.UIBuilder"]
    end

    Deploy --> Licenses
    Forms --> Licenses
    Engage --> Licenses
    Workflow --> Licenses
    UIBuilder --> Licenses
    Commerce --> Licenses

    subgraph "Integration Packages"
        FormsDeploy["Umbraco.Forms.Deploy"]
        EngageDeploy["Umbraco.Engage.Deploy"]
        EngageForms["Umbraco.Engage.Forms"]
        EngageCommerce["Umbraco.Engage.Commerce"]
        CommerceDeploy["Umbraco.Commerce.Deploy"]
    end

    FormsDeploy --> Forms
    FormsDeploy --> Deploy
    EngageDeploy --> Engage
    EngageDeploy --> Deploy
    EngageForms --> Engage
    EngageForms --> Forms
    EngageCommerce --> Engage
    EngageCommerce --> Commerce
    CommerceDeploy --> Commerce
    CommerceDeploy --> Deploy

    subgraph "Commerce Extensions"
        CommerceCheckout["Umbraco.Commerce.Checkout"]
        CommercePaymentProviders["Umbraco.Commerce.Payment.Providers"]
        CommerceShippingProviders["Umbraco.Commerce.Shipping.Providers"]
        CommerceTaxProviders["Umbraco.Commerce.Tax.Providers"]
    end

    CommerceCheckout --> Commerce
    CommercePaymentProviders --> Commerce
    CommerceShippingProviders --> Commerce
    CommerceTaxProviders --> Commerce

    subgraph "Payment Providers"
        Stripe & QuickPay & Mollie & Opayo & Klarna & Worldpay & PayPal & Buckaroo
    end
    Stripe & QuickPay & Mollie & Opayo --> CommercePaymentProviders
    Klarna & Worldpay & PayPal & Buckaroo --> CommercePaymentProviders

    subgraph "Shipping Providers"
        DHL & Shipmondo & EasyPost
    end
    DHL & Shipmondo & EasyPost --> CommerceShippingProviders

    subgraph "Tax Providers"
        TaxJar --> CommerceTaxProviders
    end
```

Explanatory notes:

* `Umbraco.Licensing` supports the older licensing mechanism for Umbraco's products, including Forms and Deploy, when used on Umbraco Cloud.
* `Umbraco.Licenses` is the newer component supporting subscription licensing, used for Forms, Workflow, Commerce, and Deploy version 12 and above when used on-premise.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.umbraco.com/umbraco-dxp/licensing-and-dependencies/commercial-product-dependencies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.