<p><strong>Currently multi-site support isn't planned.</strong></p>

<p>If you want simple multi-site-support you could use the localization feature with a custom locale. But with Craft's auto-update's and easy deployment, why would you want to use MSM anyway?</p>

<p>.</p>

<blockquote>
  <p>...we're pretty against adding it to Craft... at least in the way EE did
  it, where everything is stored on a per-site basis.</p>
  
  <p>However you should take a look at Craft's localization features. With
  that, all content can be stored on a per-locale basis, all users can
  have per-locale permissions, each locale can have its own base URL,
  templates, routes, etc.. Really is pretty powerful. The only thing
  missing is the ability to define custom locales, in the event that
  your localized sites aren't defined by territory/language, but some
  other factor. That's the main thing that's going to be changing ;)</p>
</blockquote>

<p><a href="https://plus.google.com/105300374023226628031/posts/CS2uUefs6Ah">https://plus.google.com/105300374023226628031/posts/CS2uUefs6Ah</a></p>

<p>.</p>

<blockquote>
  <p>Correct. Initially it did have an MSM-type feature, but we ended up
  taking it out, due to it overcomplicating the system.</p>
  
  <p>If you want to run multiple domains/sites off of Craft, you’ll just
  need multiple Craft installs.</p>
</blockquote>

<p><a href="https://plus.google.com/102316327373347344486/posts/71qEZ4SANhP">https://plus.google.com/102316327373347344486/posts/71qEZ4SANhP</a></p>

<p><strong>EDIT:</strong></p>

<p>You can however use one <code>craft/app/</code> folder for multiple sites. But since you'd still need multiple databases, configs, plugins, templates... it's probably not worth it, except that you would save a few bytes on files.</p>

CC BY-SA 3.0
2015-06-03T10:20:41.363Z
@VictorIn what is meant by MSM?
codecowboy
CC BY-SA 3.0
2015-06-08T21:26:55.597Z
@codecowboy Multi-Site-Manager
Victor
CC BY-SA 3.0
2016-04-08T12:27:17.203Z
We have a few customers who just want one Admin interface to login to and from there be able to switch between sites to manage content. The content pages may be different, and even different fields. And some of them like to share content between sites.

So if my understanding of Crafts localisation is correct, I dont think localisation would be a good solution because the content is managed on a per field basis in each entry. Whereas on a multisite install I may have different fields for different entry types per sites.
Laurence Cope
CC BY-SA 3.0
2016-04-08T13:01:11.823Z
@LaurenceCope no, you wouldn't need to mis-use the localization feature for this. I'd just set up the sections (shared ones and site specific ones) for  one locale. Then add environment variables to distinguish the site / environment requested from your templates. Use this info to dynamically `include` template partials, `extends` different layouts or `exit 404` requests.
carlcs
CC BY-SA 3.0
2016-04-09T15:40:14.950Z
OK great, so could be possible then. Thanks for educating me!
Laurence Cope
CC BY-SA 3.0
2017-06-15T02:17:33.860Z
This now changes with Craft 3. See https://craftcms.com/news/craft-3-multi-site
Simon East
CC BY-SA 3.0
2014-06-22T23:00:28.947Z
As someone who has had to make a secondary site the primary in an MSM install, i can truly say I wish i'd never used it. It is all good and well until you need move MSM site to a different server or hit the MySQL column limit and cant add any new fields to your MSM site. Keeping things separate does not seem like that big of a deal after having to mitigate the hell that MSM can cause.
Steve Adams
CC BY-SA 3.0
2014-06-23T12:57:14.207Z
If you're using a single craft/app/ folder, does that require additional licenses per site, or only a single license?
Jon Horton
CC BY-SA 3.0
2014-06-23T13:17:56.580Z
Good question, but I don't know. To be save ask P&T directly.
Victor
CC BY-SA 3.0
2014-06-24T13:18:53.487Z
The main reason I'm interested in a multisite install is the share-ability of data between sites. Because the 11 sites we run are closely related, multisite would allow us to to keep a central database and share data easily. Using the Locale option seems interesting, but doesn't look like it will work for completely separate sites!
Jon Horton
CC BY-SA 3.0
2014-06-24T13:38:16.630Z
If by data, you mean for example assets, you can use the same asset-source on multiple installs. -- Otherwise you could write a plugin: (1) Which connects to one central database (2) Allows you to edit the data in it's own CPsection (3) Allows access to data with a TwigExtension.
Victor
CC BY-SA 3.0
2014-10-24T02:58:09.033Z
Dragging up an old thread, but a thought regarding this discussion is that one of the main functions I've needed in the past from multiple sites is shared users/authentication. If at the least there was a plugin/core function to expose the member base with authentication you're half way there. Thoughts?
Brendan Underwood
CC BY-SA 3.0
2014-06-22T22:08:22.177Z
2014-06-22T23:35:22.013Z
2014-06-22T23:35:22.013Z
Victor
<p>We're currently using a single ExpressionEngine install with MultiSite Manager to serve up 11 total sites that share the same database. After investigating Craft, and asking <a href="https://twitter.com/craftcms/status/415220999018135552">questions via Twitter</a> it appears that multisite may not be supported.</p>

<p>Is there a way to use a single Craft install to serve up completely separate sites, or any knowledge of this being implemented in the future?</p>

CC BY-SA 3.0
2014-07-30T16:31:04.513Z
@lexyk Welcome to the Craft CMS Stack Exchange! I converted your answer here to a comment, since you were clearly asking a question and not providing an answer *to* this question.
Matt Stein
<config><plugins><server>
Are there any intentions to release multisite support for Craft?
# Are there any intentions to release multisite support for Craft?

(Asked by: username_0 on 2014-06-22)

We're currently using a single ExpressionEngine install with MultiSite Manager to serve up 11 total sites that share the same database. After investigating Craft, and asking [questions via Twitter](https://twitter.com/craftcms/status/415220999018135552) it appears that multisite may not be supported.

Is there a way to use a single Craft install to serve up completely separate sites, or any knowledge of this being implemented in the future?

**Tags:** config, plugins, server
> **Comments:**
> **username_1**: @lexyk Welcome to the Craft CMS Stack Exchange! I converted your answer here to a comment, since you were clearly asking a question and not providing an answer *to* this question.  

---

## 1 answers

### Answer by username_2 on 2014-06-22. Score: 7 | Accepted answer

**Currently multi-site support isn't planned.**

If you want simple multi-site-support you could use the localization feature with a custom locale. But with Craft's auto-update's and easy deployment, why would you want to use MSM anyway?

.

> ...we're pretty against adding it to Craft... at least in the way EE did
> it, where everything is stored on a per-site basis.
>
> However you should take a look at Craft's localization features. With
> that, all content can be stored on a per-locale basis, all users can
> have per-locale permissions, each locale can have its own base URL,
> templates, routes, etc.. Really is pretty powerful. The only thing
> missing is the ability to define custom locales, in the event that
> your localized sites aren't defined by territory/language, but some
> other factor. That's the main thing that's going to be changing ;)

<https://plus.google.com/105300374023226628031/posts/CS2uUefs6Ah>

.

> Correct. Initially it did have an MSM-type feature, but we ended up
> taking it out, due to it overcomplicating the system.
>
> If you want to run multiple domains/sites off of Craft, you’ll just
> need multiple Craft installs.

<https://plus.google.com/102316327373347344486/posts/71qEZ4SANhP>

**EDIT:**

You can however use one `craft/app/` folder for multiple sites. But since you'd still need multiple databases, configs, plugins, templates... it's probably not worth it, except that you would save a few bytes on files.

> **Comments:**
> **username_7**: As someone who has had to make a secondary site the primary in an MSM install, i can truly say I wish i'd never used it. It is all good and well until you need move MSM site to a different server or hit the MySQL column limit and cant add any new fields to your MSM site. Keeping things separate does not seem like that big of a deal after having to mitigate the hell that MSM can cause.  
> **username_0**: If you're using a single craft/app/ folder, does that require additional licenses per site, or only a single license?  
> **username_2**: Good question, but I don't know. To be save ask P&T directly.  
> **username_0**: The main reason I'm interested in a multisite install is the share-ability of data between sites. Because the 11 sites we run are closely related, multisite would allow us to to keep a central database and share data easily. Using the Locale option seems interesting, but doesn't look like it will work for completely separate sites!  
> **username_2**: If by data, you mean for example assets, you can use the same asset-source on multiple installs. -- Otherwise you could write a plugin: (1) Which connects to one central database (2) Allows you to edit the data in it's own CPsection (3) Allows access to data with a TwigExtension.  
> **username_8**: Dragging up an old thread, but a thought regarding this discussion is that one of the main functions I've needed in the past from multiple sites is shared users/authentication. If at the least there was a plugin/core function to expose the member base with authentication you're half way there. Thoughts?  
> **username_3**: @VictorIn what is meant by MSM?  
> **username_2**: @codecowboy Multi-Site-Manager  
> **username_4**: We have a few customers who just want one Admin interface to login to and from there be able to switch between sites to manage content. The content pages may be different, and even different fields. And some of them like to share content between sites.  So if my understanding of Crafts localisation is correct, I dont think localisation would be a good solution because the content is managed on a per field basis in each entry. Whereas on a multisite install I may have different fields for different entry types per sites.  
> **username_5**: @LaurenceCope no, you wouldn't need to mis-use the localization feature for this. I'd just set up the sections (shared ones and site specific ones) for  one locale. Then add environment variables to distinguish the site / environment requested from your templates. Use this info to dynamically `include` template partials, `extends` different layouts or `exit 404` requests.  
> **username_4**: OK great, so could be possible then. Thanks for educating me!  
> **username_6**: This now changes with Craft 3. See https://craftcms.com/news/craft-3-multi-site  

---

