> For the complete documentation index, see [llms.txt](https://kb.craftformswp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.craftformswp.com/plans-and-billing/managing-licenses-and-billing-info.md).

# Managing Licenses and Billing Info

We use [Freemius.com](https://freemius.com) service as our payment processing provider and license management system. All our customers has access to [Freemius User's Dashboard](https://users.freemius.com/login?next=%2Fwebsites) where they can manage the data related to their orders:

* manage billing information;
* check licenses status
* download PRO version of the product

For any questions related to billing and payment issues customers can also write directly to [**support@freemius.com**](mailto:support@freemius.com)

### License Utilization

The number of licenses purchased equals the number of sites where you can use them. However, you can also use **one free license for development site** additionally to every purchased one. This free license is automatically available after the purchase. **Practically, it means that localhost, staging and development environments will not get counted toward the license’s maximum allowed sites if its domain name is clearly a dev or staging site.**

#### TLDs that are considered as dev or staging: <a href="#tlds-that-are-considered-as-dev-or-staging" id="tlds-that-are-considered-as-dev-or-staging"></a>

* `*.dev`
* `*.test`
* `*.local`
* `*.staging`
* `*.example`
* `*.invalid`
* `*.myftpupload.com`(GoDaddy)
* `*.cloudwaysapps.com`(Cloudways)
* `*.wpsandbox.pro` (WPSandbox)
* `*.ngrok.io` (tunneling)

#### Subdomains that are considered as dev or staging: <a href="#subdomains-that-are-considered-as-dev-or-staging" id="subdomains-that-are-considered-as-dev-or-staging"></a>

* `local.*`
* `dev.*`
* `test.*`
* `stage.*`
* `staging.*`
* `stagingN.*` (SiteGround; `N`is an unsigned int)
* `*.staging.wpengine.com` (WP Engine)
* `dev-*.pantheonsite.io`(Pantheon)
* `test-*.pantheonsite.io` (Pantheon)
* `staging-*.kinsta.com` (Kinsta)
* `staging-*.kinsta.cloud` (Kinsta)
* `*.mystagingwebsite.com'` (Pressable)

Additionally, if your domain is `localhost` (with any port), it will also be treated as a localhost domain.

**If you want to utilize a license on a dev site that doesn’t fit the criteria listed above you can deactivate the license from within the Accout page in their WP Admin dashboard, and then reuse the license.**

### Prorations and upgrades <a href="#prorations-and-upgrades" id="prorations-and-upgrades"></a>

**For lifetime license holders**

In case you want to upgrade your lifetime license from 1 site to 3 sites or 25 sites, there is **a special period of one week** after the initial purchase when you can do such upgrade as upgrade. It means you will just have to pay the difference between the prices of the license. After that you cannot upgrade with proration, but only buying a new license for the full price.

**For annual license holders:**

Similar to the terms described for lifetime license holders, there is **a special period of one week** after the initial purchase when you can do upgrade just by paying the difference. So, plan your purchase in advance ;)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://kb.craftformswp.com/plans-and-billing/managing-licenses-and-billing-info.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.