[Feature Request]: Support for multi-tenant applications with subdomains

[AKurka]

Feature Description

Hello,

It would be really helpful if Expose could support sharing multi-tenant applications that rely on subdomains.

For example, I’m currently working with a Laravel multi-tenant setup using the Stancl/tenancy
package. In this setup, I have:

A central domain: app.mydomain.test

Tenant domains: tenant1.mydomain.test, tenant2.mydomain.test, etc.

At the moment, Expose only seems to handle a single domain, which makes it difficult to test and share applications that depend on multiple subdomains for different tenants.

It would be great if Expose could:

• Allow mapping and exposing multiple local subdomains at once
• Handle dynamic tenant subdomains (e.g., *.mydomain.test)
• Provide a way to share these publicly while keeping the subdomain routing intact

This would make Expose much more powerful for developers building and testing multi-tenant applications.

Thanks for considering this feature!

Is this feature valuable for other users as well and why?

Multi-tenant applications are increasingly common, especially in SaaS products where each customer has their own subdomain. Frameworks like Laravel, Rails, and Django all have popular multi-tenancy packages that rely on subdomain routing.

Currently, developers working on such projects struggle to share their local environment because tools like Expose don’t natively support multiple subdomains or wildcard domains. Supporting this would:

Help SaaS developers demo their product to clients or teammates.

Make it easier to test tenant-specific behavior without complex reverse proxy setups.

Provide parity with production environments, where wildcard subdomains are the standard.

In short, adding support for multi-tenant / subdomain routing would benefit any developer building SaaS or multi-tenant apps, not just in Laravel but across different stacks.