railway-domain▌
davila7/claude-code-templates · updated Apr 8, 2026
Add, view, or remove domains for Railway services.
Railway Domain Management
Add, view, or remove domains for Railway services.
When to Use
- User asks to "add a domain", "generate a domain", "get a URL"
- User wants to add a custom domain
- User asks "what's the URL for my service"
- User wants to remove a domain
Add Railway Domain
Generate a railway-provided domain (max 1 per service):
railway domain --json
For a specific service:
railway domain --json --service backend
Response
Returns the generated domain URL. Service must have a deployment.
Add Custom Domain
railway domain example.com --json
Response
Returns required DNS records:
{
"domain": "example.com",
"dnsRecords": [
{ "type": "CNAME", "host": "@", "value": "..." }
]
}
Tell user to add these records to their DNS provider.
Read Current Domains
Use railway-environment skill to see configured domains, or query directly:
query domains($envId: String!) {
environment(id: $envId) {
config(decryptVariables: false)
}
}
Domains are in config.services.<serviceId>.networking:
serviceDomains- Railway-provided domainscustomDomains- User-provided domains
Remove Domain
Use railway-environment skill to remove domains:
Remove custom domain
{
"services": {
"<serviceId>": {
"networking": {
"customDomains": { "<domainId>": null }
}
}
}
}
Remove railway domain
{
"services": {
"<serviceId>": {
"networking": {
"serviceDomains": { "<domainId>": null }
}
}
}
}
Then use railway-environment skill to apply and commit the change.
CLI Options
| Flag | Description |
|---|---|
[DOMAIN] |
Custom domain to add (omit for railway domain) |
-p, --port <PORT> |
Port to connect |
-s, --service <NAME> |
Target service (defaults to linked) |
--json |
JSON output |
Composability
- Read domains: Use railway-environment skill
- Remove domains: Use railway-environment skill
- Apply removal: Use railway-environment skill
- Check service: Use railway-service skill
Error Handling
No Service Linked
No service linked. Use --service flag or run `railway service` to select one.
Domain Already Exists
Service already has a railway-provided domain. Maximum 1 per service.
No Deployment
Service has no deployment. Deploy first with `railway up`.
Invalid Domain
Invalid domain format. Use a valid domain like "example.com" or "api.example.com".
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★53 reviews- ★★★★★Sofia Smith· Dec 28, 2024
railway-domain fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Maya Huang· Dec 28, 2024
Registry listing for railway-domain matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kiara Gonzalez· Dec 20, 2024
railway-domain is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Pratham Ware· Dec 4, 2024
railway-domain has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Harper Kim· Dec 4, 2024
Solid pick for teams standardizing on skills: railway-domain is focused, and the summary matches what you get after install.
- ★★★★★Yash Thakker· Nov 23, 2024
Solid pick for teams standardizing on skills: railway-domain is focused, and the summary matches what you get after install.
- ★★★★★Michael Iyer· Nov 23, 2024
railway-domain has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Benjamin Gupta· Nov 19, 2024
Useful defaults in railway-domain — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Michael Ghosh· Nov 19, 2024
I recommend railway-domain for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Maya Harris· Nov 19, 2024
railway-domain reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 53