If I'm not mistaken (haven't checked the code yet) subdomains are rewritten in the middleware to map onto /app/[tenant]/... then your code can consume it as a path parameter.

thanks, this was exactly what I was looking for! I do have one issue though, when admin.example.com (or app. as per the example) doesn't have a page but [tenant].example.com does, the router thinks that admin is another tenant

accessing example.com/admin/a (rewritten from admin.example.com/a) it matches the page under [tenant], I would like that to simply generate a 404 instead

[...404]/page.tsx did the trick :)

How can I do this without having to use vercel? I use my own VPS because I host other things on it as well like discord bots and such. The guide on the platforms starter kit just walks you through doing it for vercel. Would I just need to start digging through source code on the github to find the rewrite mechanism?

it works perfectly when running locally too, this doesn't require vercel at all

The gist is that the middleware just rewrites tenant.domain.com/path in most cases to /[tenant]/path matching your hierarchy in the file system.

I got it to match the main domain, but I'm now having fun with apache trying to get it to route to the subdomains.

You just send all requests of the shape *.domain.com to the Next app and let it deal with subdomains.

I have my configuration set up like that, but when I go to a subdomain it fails to load anything

I'm stuck at work overnight so I'll have to test tomorrow

I got it working, thanks for the help! My tired brain messed up the folder setup in the middleware

how did you figure it out?