PromptShip
Migration guide

Migrate from Expo to PromptShip

Most Expo apps end up stitched to a separate backend host plus a separate database service plus a separate cache, and they pay EAS for builds on top. PromptShip collapses backend and databases into one platform you drive from your AI IDE. Keep EAS for your mobile builds.

What you can do today

  • Backend: full replacement. Persistent containers, managed Postgres, a Redis-compatible cache, and ClickHouse, none of which Expo provides. EAS Hosting covers edge functions and domains; it isn't a persistent backend.
  • Android and iOS builds: keep EAS. PromptShip hosts the backend; EAS keeps building and submitting the app.
  • Expo SDK / React Native libraries stay exactly where they are, they're a runtime library, not a hosting choice. You keep expo-router, the Expo SDK modules, and OTA tooling regardless.

PromptShip vs Expo / EAS

PromptShipExpo / EAS
OTA / over-the-air updates✕✓
Persistent backend containers✓✕
Managed Postgres✓✕
Managed Redis-compatible cache✓✕
WebSockets, workers, cron✓✕
Predictable tier pricing✓subscription
MCP-native deploys from AI IDE✓✕

Setup in your AI IDE

  1. 1. Add the PromptShip MCP to Claude Code, Cursor, or Codex.
  2. 2. Generate or import the backend. Whatever stack fits the app, Node, Python, Go.
  3. 3. Deploy via MCP. Postgres + Redis attach in seconds.
  4. 4. Mobile builds: keep EAS.
Get started

Run your Expo app on PromptShip

Persistent containers, managed Postgres + Redis. Free during early access.

[ Join the waitlist ]

Already have access? Install the MCP

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