Comparison

PromptShip vs Cloud Run

PromptShip and Cloud Run are in the same category: managed container runtimes that take a Docker image and run it. They differ on how you deploy, how you pay, and what comes attached.

PromptShip is not a wrapper around Cloud Run. We operate our own platform end to end, build pipeline, runtime, and managed databases. The two products are alternatives, not layers.

Feature comparison

	PromptShip	Cloud Run
Standard Docker images	✓	✓
Persistent containers, no cold starts	✓	min instances
Auto-SSL on custom domains	✓	✓
Managed Postgres attached	✓	Cloud SQL, separate
Managed Redis-compatible cache	✓	Memorystore, separate
ClickHouse analytics	✓	✕
MCP-native deploys from AI IDE	✓	✕
Per-request billing	✕	✓
Predictable tier pricing	✓	✕
Mobile (Google Play) submission built in	✓	✕

When Cloud Run is the right choice

• You're already on Google Cloud and want tight integration with the rest of GCP.
• You're fine assembling Cloud SQL, Memorystore, and IAM yourself.
• Per-request billing actually fits your workload (very spiky, mostly idle).

When PromptShip is the right choice

• You build in Claude Code, Cursor, or Codex and want to deploy from inside the conversation via MCP.
• You want Postgres, Redis, and ClickHouse attached without separate provisioning steps.
• You want predictable tier pricing instead of per-request billing.
• You also need to ship a mobile app to Google Play.

Try PromptShip instead of Cloud Run

Same category, MCP-native deploys, attached databases, and predictable pricing. Free during early access.

Join Waitlist

Already have access? Install the MCP:

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