> 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.md).

# Billing and Plans

The Management Console offers two plans, the free Community Plan and a paid Enterprise Plan. Every company starts on the Community Plan by default.

Enterprise customers are upgraded to the Enterprise Edition by the UMH Team. Enterprise licenses are time-limited. The expiry date matches the subscription term in your agreement with the UMH Team. The Enterprise plan is applied on a per-company basis, allowing you to invite users without extra cost.

You can see which plan your company is in three places:

* The sidebar shows Enterprise Edition or Community Edition under the Management Console name.
* Settings → Account has a License field. The field says `Inactive` if you have the Community Plan. As an enterprise customer, that field will show you the expiry date of your Enterprise license.
* Enterprise Only: The License Status card on the home page shows Active or Inactive. For an active license, the card also shows Valid until with the expiry date, which turns red when fewer than 90 days remain.

## What the plans include

On the free Community Plan, your company can register exactly one instance.

The Enterprise Plan lets you register an unlimited amount of instances and includes user management, the Enterprise release channel, and version control features.

You can find every difference between the two plans in the [plan comparison](/management-console/billing-and-plans/plan-comparison.md).

## How to get an Enterprise license

As part of our white-glove onboarding process, UMH attaches the license to your company for you, and from then on every user in your company is on the Enterprise Plan.

If you are interested in an Enterprise license, [you can get in touch with us through this form](https://www.umh.app/talk-to-team).

### What to do when the Enterprise license expires

After the expiry date, your company automatically gets the Community Plan.

Once your company is back on the Community Plan:

* Your existing instances keep running and stay connected, and nothing is deleted. However, you can't register more instances.
* Your existing users keep their accounts and roles. However, you can't invite new people to your company.
* Every other Enterprise control listed in the [plan comparison](/management-console/billing-and-plans/plan-comparison.md) is disabled.
* Your data stays yours, regardless of plan. A plan change does not touch the data on your instances.

Our team will get in touch with you prior to your license expiring. If you'd like to proactively discuss your renewal period, reach out to your Account Executive.


---

# 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.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.
