> For the complete documentation index, see [llms.txt](https://docs.yaycommerce.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yaycommerce.com/manual/licensing/local-development.md).

# Local development

YayCommerce license keys allow activation on local development domains and IPs without affecting the activation limit totals.&#x20;

* Local sites can be activated without being counted toward the activation limit.
* Local website URLs are logged for tracking purposes.

<figure><img src="/files/zxneFHvKjQZ02E2z41cM" alt=""><figcaption><p>Local activations are not counted toward the activation limit</p></figcaption></figure>

This offer ensures that developers can work on projects seamlessly without using up license activations.&#x20;

## **Local/ staging sites**

All license keys allow local development domains and IPs to be activated without counting towards the activation limit totals. The development URL will still be logged.

We detect these types of domains as development sites:

* `localhost`
* `127.0.0.1`
* `.dev`&#x20;
* `.local`
* `.test`
* `.staging`&#x20;
* `staging-yourshop.`&#x20;
* `yourshop.wpengine.com`
* `yourshop.`[`cloudwaysapps.com`](http://cloudwaysapps.com/)
* `yourshop.`[`flywheelsites.com`](http://flywheelsites.com/)
* `yourshop.`[`flywheelstaging.com`](http://flywheelstaging.com/)
* `yourshop.`[`myftpupload.com`](http://myftpupload.com/)
* `.kinsta.cloud`
* `.instawp.xyz`&#x20;

To make it easier, please access <https://yaycommerce.com/how-to-check-if-a-site-is-local/>  to verify if your staging sites can activate the license key.&#x20;

If you have trouble activating a single license key on your staging or development environment, please chat with [YayCommerce support team](https://yaycommerce.com/support/) for assistance.


---

# 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://docs.yaycommerce.com/manual/licensing/local-development.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.
