Migration guide

Migrate from Railway to PromptShip

Railway gets a lot right, persistent containers, real backends, decent ergonomics. The places people leave Railway are usually the bill (usage-based pricing that surprises you on a busy month) and the gap between writing code in Claude Code or Cursor and actually getting it deployed. PromptShip closes both.

What changes

Predictable tier pricing. Pick a tier, see the price. No per-second usage math, no end-of-month surprise.
MCP-native deploys. Add the PromptShip MCP to your AI IDE and deploy from inside the conversation. No copying terminal commands, no separate dashboards.
Postgres, Redis, ClickHouse attached natively, not as separate plugins. ClickHouse in particular is rare on competitor platforms.
Mobile publishing. Google Play submission via submit_app, useful if you also ship a React Native or Kotlin app.

PromptShip vs Railway

	PromptShip	Railway
Persistent containers, no cold starts	✓	✓
Predictable tier pricing (no usage meters)	✓	✕
MCP-native deploys from Claude Code / Cursor	✓	✕
Managed Postgres	✓	✓
Managed Redis-compatible cache	✓	✓
Managed ClickHouse analytics	✓	✕
Mobile (Google Play) publishing built in	✓	✕
Standard Docker, no lock-in	✓	✓

Migration steps

1. Add the PromptShip MCP to your AI IDE.
2. Connect your GitHub repo, same repo you deployed on Railway.
3. Attach the databases you need via MCP, Postgres, Redis, ClickHouse.
4. Point your domain at the new app, verify, decommission Railway.

Move from Railway to PromptShip

Predictable pricing, MCP-native deploys, and managed databases included. Free during early access.

Join Waitlist

Already have access? Install the MCP:

$ claude mcp add --transport http promptship https://mcp.promptship.dev/mcp