Thanks for the suggestion! We can definitely see why this would make managing multiple apps much more convenient.
At the moment, Teable supports assigning a separate custom subdomain to each app. Using path-based URLs (such as app.mydomain.com/super-app1) isn’t available, and we don’t currently have plans to support this.
We appreciate you taking the time to share the idea.
Hi Leo - thanks for your soon reply. Can you shed some light into the decision so that I can understand it? Is it technically much more complicated? I’m using a landing pages builder who makes personalized pages on scale, there it’s possible to have a path-based URLs and it’s super convenient and looks imo more professional (eg mydomain.com/client-name)
It’s not that we think path-based URLs aren’t useful—we can definitely see the appeal. It’s simply not something we’re planning to support at this time, so we haven’t invested in designing or implementing that approach.
We’ll keep your feedback in mind if we revisit our custom domain capabilities in the future. Thanks again for taking the time to explain your use case.