2 months ago
Hi Railway team,
I've hit the 20 custom domain per service limit on my Pro plan and would like to request an increase.
Context:
- Plan: Pro
- Project: twcako-production
- Service: web (Django 5.2 / Python 3.12)
- Current usage: 20 of 20 custom domains
We run a multi-tenant platform where each merchant gets their own branded storefront on their own root domain, plus a www record and a dashboard subdomain. Current merchants include bkmood.com, skinamazingph.com, and nutridelph.com. All domains are proxied through Cloudflare and resolving correctly, so this is purely a quota issue and not a configuration problem.
Requested new limit: 100 custom domains on this service.
We expect to onboard additional merchants over the next few months, so a higher ceiling would let us provision without opening a new request each time. Happy to provide any account details you need.
Two related questions while I have you:
-
Does a wildcard domain (e.g. *.bkmood.com) count as one entry against the limit, or does it count per resolved subdomain? I'm planning to consolidate www and dash subdomains under wildcards to reduce entry count.
-
Is Cloudflare for SaaS (Custom Hostnames) supported as a path for multi-tenant custom domains on Railway? I've seen reports of requests returning 404 with x-railway-fallback: true when proxied this way. If there's a supported pattern for this, I'd rather build on that than keep adding domains manually. If the TCP Proxy route is the recommended approach, I'd appreciate confirmation.
Thanks,
Ed
1 Replies
2 months ago
The Pro plan custom domain limit is 20 per service, and we don't increase it for multi-tenant use cases at this scale. The recommended path for platforms onboarding merchants with their own domains is to manage those domains externally through Cloudflare (which you're already using) and proxy traffic to your Railway service, rather than registering each one individually in Railway. A wildcard domain like *.bkmood.com counts as a single entry against the limit and covers all subdomains with one certificate, so consolidating www and dash under wildcards would reduce your per-merchant count. For whether Cloudflare for SaaS (Custom Hostnames) works cleanly as the proxy layer here, that's a third-party integration detail we can't speak to authoritatively, but the community has hands-on experience with that pattern and can help with tested configurations.
Status changed to Awaiting User Response Railway • about 2 months ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago