Railway through Squiid

What Railway is

Railway runs whatever your app actually is. Point it at a repository and it detects the language, builds a container and deploys it with a public domain, or give it a Dockerfile and it runs that. The same project can hold a web service, a background worker, a cron job and a Postgres, Redis or MySQL database, wired together with service variables rather than copied connection strings, and environments let a staging copy of everything exist alongside production. Deployments keep a history you can roll back to, and logs and metrics per service are part of the dashboard rather than an add-on.

This is the host for AI-coded projects that are not just a frontend. A Python FastAPI service, a Node worker consuming a queue, a Discord bot, a scraping job, or a long-running process that a serverless platform would time out all fit here without rearchitecting them into functions. It is also a common landing place when an agent writes something in a language the frontend hosts do not support. Because databases are services in the same project, the connection string is injected as a variable instead of being copied by hand.

Why connect it through Squiid

Railway is on the Squiid roadmap. When it is connected, Squiid will provision the project, hold the API token and route deploys and management through https://api.squiid.io/v1/railway/... with Authorization: Bearer $SQUIID_API_KEY, with the Railway CLI working by base URL swap (gateway convention). The Hobby plan passes through at $5 a month at Railway's listed price with no Squiid fee, and compute, memory and network usage meter against prepaid credits at list on your single invoice.

• One account, one key, one bill, one dashboard. Railway sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Railway credentials. Your code carries SQUIID_API_KEY, so RAILWAY_TOKEN, RAILWAY_PROJECT_ID, RAILWAY_ENVIRONMENT never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Railway costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• A provisioned Railway project with the token held by Squiid
• Deploy from a repo or a Dockerfile
• Web services, workers, crons and databases together
• Usage metered against prepaid credits
• Hobby at $5 a month passed through at list price

How to connect Railway

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces RAILWAY_TOKEN, RAILWAY_PROJECT_ID, RAILWAY_ENVIRONMENT
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/railway/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Railway charges a small plan fee plus per-minute CPU, memory, storage and network usage, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Railway usage, with no markup and no per-request margin.

Railway Hobby passes through at $5 a month at the provider’s listed price on your monthly Squiid invoice. Service subscriptions carry no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Railway usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: the app is redeployed from your own source into your own Railway account, then domains and environment variables are re-pointed. Squiid never owns your code, your schema or your domain, and the gateway speaks Railway's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Railway through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Railway usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.