<p>Sebastian, you can always work locally "for free", using "craft.dev" as host name.</p>

<p>Check the FAQs here at the bottom of the pricing page <a href="https://buildwithcraft.com/pricing">https://buildwithcraft.com/pricing</a></p>

<p>MAMP PRO makes it really easy to setup custom host names, btw. </p>

CC BY-SA 3.0
2015-04-01T15:16:09.117Z
This also works with subdomains of `craft.dev` (→ [Try out Craft Client and Pro on multiple development URLs?](http://craftcms.stackexchange.com/q/4368/125)).
carlcs
CC BY-SA 3.0
2015-06-17T21:04:37.350Z
**UPDATE:** It's now possible to try Craft Client from _any_ non-public domain: http://pixelandtonic.com/blog/test-craft-client-pro-from-any-non-public-domain
Lindsey D
CC BY-SA 3.0
2015-04-01T15:09:49.890Z
2015-04-01T15:09:49.890Z
tom
<p>When you move the license to production you'll see a warning in the CP - you then have the option to transfer the license to the new domain.  See <a href="http://buildwithcraft.com/help/license-transferring" rel="nofollow">here</a> for more info.</p>

<p>Obviously then you'll get the warning in your development environment but that's something you can live with I assume!</p>

CC BY-SA 3.0
2015-04-01T17:12:42.417Z
2015-04-01T17:58:15.857Z
2015-04-01T17:58:15.857Z
Adam Gilleard
<p>Short answer is <strong>yes, that is entirely allowed</strong>. Great information has already been provided in <a href="https://craftcms.stackexchange.com/a/8964/45">Tom's answer</a> and <a href="https://craftcms.stackexchange.com/a/8969/45">Adam's answer</a>.</p>

<p>If you are already certain that you'll be purchasing a Craft Client account, then you won't have to do anything special to get the site working locally. As long as the same <strong>license key</strong> remains in your site, any purchased upgrades will remain available to you... regardless of whether the site is running locally or on a server!</p>

<p>Not sure how familiar you are with this, but you may want to learn more about <a href="http://buildwithcraft.com/docs/multi-environment-configs" rel="nofollow noreferrer">multi-environment configurations</a> in Craft. It's incredibly easy to move your website between environments without losing any rights or privileges.</p>

<p>You can run your site locally without any warnings as long as you're using a <strong>dev-sounding</strong> domain. Read this article... All of the answers you're looking for should be in here:</p>

<blockquote>
  <p><a href="http://buildwithcraft.com/help/license-enforcement" rel="nofollow noreferrer">How is Craft’s license agreement enforced?</a></p>
</blockquote>

CC BY-SA 3.0
2015-04-01T17:34:00.123Z
2015-04-01T17:34:00.123Z
2017-04-13T12:51:00.253Z
Lindsey D
<p>Any non-public domain will do the job. Just hit Upgrade in your CP then you'll get a option to use it for free as long as you work on a non-public domain so localhost works fine. </p>

<p>When you transfer it to a public domain and you used Craft Pro only options you have to get a license to keep it up like you did on the dev version.</p>

CC BY-SA 3.0
2015-09-15T09:01:23.500Z
2015-09-15T09:01:23.500Z
Justin Dekkers
<p>Is there any problem with buying a Craft Client account, working on the website locally (on my pc), and when it´s done move it to the server?</p>

<p>Is this permitted by the license?</p>

<license>
Craft license and develop a website locally?
# Craft license and develop a website locally?

(Asked by: username_0 on 2015-04-01)

Is there any problem with buying a Craft Client account, working on the website locally (on my pc), and when it´s done move it to the server?

Is this permitted by the license?

**Tags:** license


---

## 4 answers

### Answer by username_1 on 2015-04-01. Score: 6

username_0, you can always work locally "for free", using "craft.dev" as host name.

Check the FAQs here at the botusername_1 of the pricing page <https://buildwithcraft.com/pricing>

MAMP PRO makes it really easy to setup cususername_1 host names, btw.

> **Comments:**
> **username_2**: This also works with subdomains of `craft.dev` (→ [Try out Craft Client and Pro on multiple development URLs?](http://craftcms.stackexchange.com/q/4368/125)).  
> **username_3**: **UPDATE:** It's now possible to try Craft Client from _any_ non-public domain: http://pixelandtonic.com/blog/test-craft-client-pro-from-any-non-public-domain  

---

### Answer by username_4 on 2015-04-01. Score: 5

When you move the license to production you'll see a warning in the CP - you then have the option to transfer the license to the new domain. See [here](http://buildwithcraft.com/help/license-transferring) for more info.

Obviously then you'll get the warning in your development environment but that's something you can live with I assume!


---

### Answer by username_3 on 2015-04-01. Score: 3

Short answer is **yes, that is entirely allowed**. Great information has already been provided in [Tom's answer](https://craftcms.stackexchange.com/a/8964/45) and [Adam's answer](https://craftcms.stackexchange.com/a/8969/45).

If you are already certain that you'll be purchasing a Craft Client account, then you won't have to do anything special to get the site working locally. As long as the same **license key** remains in your site, any purchased upgrades will remain available to you... regardless of whether the site is running locally or on a server!

Not sure how familiar you are with this, but you may want to learn more about [multi-environment configurations](http://buildwithcraft.com/docs/multi-environment-configs) in Craft. It's incredibly easy to move your website between environments without losing any rights or privileges.

You can run your site locally without any warnings as long as you're using a **dev-sounding** domain. Read this article... All of the answers you're looking for should be in here:

> [How is Craft’s license agreement enforced?](http://buildwithcraft.com/help/license-enforcement)


---

### Answer by username_5 on 2015-09-15. Score: 0

Any non-public domain will do the job. Just hit Upgrade in your CP then you'll get a option to use it for free as long as you work on a non-public domain so localhost works fine.

When you transfer it to a public domain and you used Craft Pro only options you have to get a license to keep it up like you did on the dev version.


---

