# Creating Custom Subdomain

**URL:** <https://community.weweb.io/t/creating-custom-subdomain/942>\
**Category:** How do I?\
**Created:** [August 8, 2022, 8:56am UTC](https://community.weweb.io/t/creating-custom-subdomain/942 "2022-08-08T08:56:07Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![khairul](https://avatars.discourse-cdn.com/v4/letter/k/a88e4f/32.png) [@khairul](https://community.weweb.io/u/khairul)\
**Post date:** [August 8, 2022, 8:56am UTC](https://community.weweb.io/t/creating-custom-subdomain/942/1 "2022-08-08T08:56:07Z")

</div>

Hi, is it possible to create a custom subdomain with weweb? For example, I want every users to have a custom subdomain for example [user1.domain.com](http://user1.domain.com), [user2.domain.com](http://user2.domain.com), and so on. Is it possible and how can I do it?

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [August 9, 2022, 7:08am UTC](https://community.weweb.io/t/creating-custom-subdomain/942/2 "2022-08-09T07:08:05Z")

</div>

Hi @khairul 👋

No, we currently can set only one subdomain per project.

It’s a super interesting use case though! May I ask what you would like to build?

---

<div class="post-metadata">

**Author:** ![khairul](https://avatars.discourse-cdn.com/v4/letter/k/a88e4f/32.png) [@khairul](https://community.weweb.io/u/khairul)\
**Post date:** [August 9, 2022, 7:51am UTC](https://community.weweb.io/t/creating-custom-subdomain/942/3 "2022-08-09T07:51:47Z")

</div>

I am trying to build an alternative version of shopify, something with a little different approach, if I can make a subdomain for every user/shop that would be great

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [August 9, 2022, 9:08am UTC](https://community.weweb.io/t/creating-custom-subdomain/942/4 "2022-08-09T09:08:02Z")

</div>

Sounds cool!

Just shared your use case with our product team so they have it in mind 🙂

---

<div class="post-metadata">

**Author:** ![michaeln](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/michaeln/32/8078_2.png) [@michaeln](https://community.weweb.io/u/michaeln)\
**Post date:** [July 28, 2023, 5:00pm UTC](https://community.weweb.io/t/creating-custom-subdomain/942/5 "2023-07-28T17:00:19Z")

</div>

Is it still the case that you can only publish to one subdomain? Also, what is the process for splitting the app such that some pages go to the domain and others are only applicable to the subdomain?

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [August 16, 2023, 5:13pm UTC](https://community.weweb.io/t/creating-custom-subdomain/942/6 "2023-08-16T17:13:27Z")

</div>

> [@michaeln](#):
>
> Is it still the case that you can only publish to one subdomain?

Yes. There’s definitely no way to publish pages from the same project to different domains at the moment.

To publish the same project on multiple domains, you can’t do it in WeWeb but @jaredgibb shared [this resource](https://community.weweb.io/t/tutorial-how-to-link-a-custom-domain-to-a-weweb-app/214/12) in a different thread and seemed happy with it!

It’s not affiliated to us and we haven’t tried it so can’t promise anything but perhaps worth a try 🙂

---

<div class="post-metadata">

**Author:** ![Oliver](https://avatars.discourse-cdn.com/v4/letter/o/85f322/32.png) [@Oliver](https://community.weweb.io/u/Oliver)\
**Post date:** [November 24, 2023, 12:36pm UTC](https://community.weweb.io/t/creating-custom-subdomain/942/7 "2023-11-24T12:36:57Z")

</div>

Hello, is there any news here?

---

<div class="post-metadata">

**Author:** ![Antiokh](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/antiokh/32/2794_2.png) [@Antiokh](https://community.weweb.io/u/Antiokh)\
**Post date:** [November 25, 2023, 12:29am UTC](https://community.weweb.io/t/creating-custom-subdomain/942/8 "2023-11-25T00:29:50Z")

</div>

I have the same question, but with another usecase: I want to make some sections of a web portal, starting from the 3rd level domain.

4ex: [www.domain.com](http://www.domain.com) — is an alias of [domain.com](http://domain.com)  
[business.domain.com](http://business.domain.com) — is a part for entrepreneurs.  
[events.domain.com](http://events.domain.com) — events list.

In PHP/Apache it can be done with mod\_rewrite, pointing folder /business/ to a subdomain business.

Now we can only build different projects on the same database to implement it.

---

<div class="post-metadata">

**Author:** ![SnitchNewt](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/snitchnewt/32/5925_2.png) [@SnitchNewt](https://community.weweb.io/u/SnitchNewt)\
**Post date:** [November 25, 2023, 5:27pm UTC](https://community.weweb.io/t/creating-custom-subdomain/942/9 "2023-11-25T17:27:15Z")

</div>

I have the same requirement for needing custom subdomains and also multiple domains. We built a multi-tenant SaaS application and our clients want to white-label so that their customers stay “within their website” since it is more trusted when the URL in the address bar is recognized by by their users.

Alternative things we have considered (and tried) already:

1. **HTTP redirect** : The URL in the address bar changes. Requires URL parameters to handle different tenants. Have to design app without relying/using URL parameters.
2. **Domain forwarding** : The URL in the address bar changes. Requires URL parameters to handle different tenants. Have to design app without relying/using URL parameters.
3. **Landing page with tenant selection** : Okay for up to 5 tenants. Starts to look like an advertising board with more tenants and their logos displayed.
4. **Domain forwarding with frame redirect** : The URL in the address bar stays the same (good). Many other issues with this including CORS, URL parameters don’t work, etc.
5. **Reverse Proxy** : Still trying to get this to work. Problem is that all clients may have to learn to set this up themselves, which doesn’t seem like a fun exercise.
6. **[https://coalias.com](https://coalias.com)**: Debating whether to go this route due to not knowing reputation of the service and what kinds of data is stored/logged.

---

<div class="post-metadata">

**Author:** ![raydeck](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/raydeck/32/384_2.png) [@raydeck](https://community.weweb.io/u/raydeck)\
**Post date:** [November 25, 2023, 6:35pm UTC](https://community.weweb.io/t/creating-custom-subdomain/942/10 "2023-11-25T18:35:36Z")

</div>

A couple of members have done this with the help [of our office hours at State Change](https://statechange.ai). Weweb is a first class editor but the hosting service is not that sophisticated. Using the self-hosting and code export options that comes with either annual contracts or their enterprise plan lets you host elsewhere that provides these features. Our members chose [Digital Ocean](https://digitalocean.com), but there are others too!

---

<div class="post-metadata">

**Author:** ![Antiokh](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/antiokh/32/2794_2.png) [@Antiokh](https://community.weweb.io/u/Antiokh)\
**Post date:** [November 27, 2023, 12:53am UTC](https://community.weweb.io/t/creating-custom-subdomain/942/11 "2023-11-27T00:53:34Z")

</div>

Reverse proxy isn’t so complex when you use nginx, but nginx works good only on Linux configs. You can generate configs and just take care of ssl sertificates.

---

<div class="post-metadata">

**Author:** ![jbarrera](https://avatars.discourse-cdn.com/v4/letter/j/4da419/32.png) [@jbarrera](https://community.weweb.io/u/jbarrera)\
**Post date:** [April 15, 2024, 10:47pm UTC](https://community.weweb.io/t/creating-custom-subdomain/942/12 "2024-04-15T22:47:42Z")

</div>

Of the 6 options you tried, did you choose any? If so, which one was it? I’m looking to build a multi-tenant whitelabel platform and I want to be clear about how I can solve this.

---

<div class="post-metadata">

**Author:** ![SnitchNewt](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/snitchnewt/32/5925_2.png) [@SnitchNewt](https://community.weweb.io/u/SnitchNewt)\
**Post date:** [April 16, 2024, 4:51am UTC](https://community.weweb.io/t/creating-custom-subdomain/942/13 "2024-04-16T04:51:05Z")

</div>

I ended up choosing #3, which was a landing page with a tenant selection.

---

<div class="post-metadata">

**Author:** ![Alsamarain](https://avatars.discourse-cdn.com/v4/letter/a/9dc877/32.png) [@Alsamarain](https://community.weweb.io/u/Alsamarain)\
**Post date:** [March 26, 2025, 6:04pm UTC](https://community.weweb.io/t/creating-custom-subdomain/942/14 "2025-03-26T18:04:45Z")

</div>

This is the last issue preventing me from moving our application to WeWeb. Our clients have sub-divisions and are (very) precious about maintaining their autonomy through using a subdomain for their profiles. Is there anything in the pipeline for this to be achievable natively? Would be greatly appreciated!

---

<div class="post-metadata">

**Author:** ![Broberto](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/broberto/32/5918_2.png) [@Broberto](https://community.weweb.io/u/Broberto)\
**Post date:** [March 26, 2025, 9:19pm UTC](https://community.weweb.io/t/creating-custom-subdomain/942/15 "2025-03-26T21:19:04Z")

</div>

I don’t think so, setting a proxy is not that hard either

---

<div class="post-metadata">

**Author:** ![Joyce](https://sea2.discourse-cdn.com/flex016/user_avatar/community.weweb.io/joyce/32/13232_2.png) [@Joyce](https://community.weweb.io/u/Joyce)\
**Post date:** [March 28, 2025, 12:24am UTC](https://community.weweb.io/t/creating-custom-subdomain/942/16 "2025-03-28T00:24:09Z")

</div>

Hi @Alsamarain 👋

Broberto is right. This is not planned on the roadmap for the moment but I can add your thoughts to the existing product ticket in our backlog.

Can you tell me a bit more about the project(s) that would require this feature and why you would need the feature natively/the existing workarounds are not an option for you?
