> For the complete documentation index, see [llms.txt](https://docs.umh.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umh.app/management-console/billing-and-plans/plan-comparison.md).

# Plan Comparison

The table below lists the available features of our Community and Enterprise plans. Plans are applied to every user and every instance of a company.

To learn more about how plans work at UMH, see [Billing and Plans](/management-console/billing-and-plans.md). If you are interested in our Enterprise plan, see [How to get an Enterprise license](/management-console/billing-and-plans.md#how-to-get-an-enterprise-license).

| **Feature**                                            | Community Plan | Enterprise Plan                                                                                |
| ------------------------------------------------------ | -------------- | ---------------------------------------------------------------------------------------------- |
| Host your own Unified Namespace                        | ✓              | ✓                                                                                              |
| Management Console Access                              | ✓              | ✓                                                                                              |
| 70+ bridge templates                                   | ✓              | ✓                                                                                              |
| Versioning for Data Models                             | ✓              | ✓                                                                                              |
| Users per company                                      | 1              | ∞                                                                                              |
| Instances per company                                  | 1              | ∞                                                                                              |
| Enterprise Release Channel                             | —              | ✓                                                                                              |
| Roles and location permissions                         | —              | [Admin, Editor and Viewer roles](/management-console/users-and-permissions/roles-reference.md) |
| Review changes before a deploy with a visual diff view | —              | ✓                                                                                              |
| Instance audit logs                                    | —              | Paid add-on                                                                                    |
| Single sign-on with your own identity provider         | —              | [Paid add-on](/management-console/authentication/enterprise-sso.md)                            |


---

# 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.umh.app/management-console/billing-and-plans/plan-comparison.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.