moai-platform-deployment

Configure and deploy applications to Vercel, Railway, and Convex platforms.

2|Updated May 27, 2026
One-click install
npx skills add https://github.com/yekinya/moai-novel --skill moai-platform-deployment-yekinya
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-platform-deployment
Source: https://github.com/yekinya/moai-novel/tree/main/moai-novel/.claude/skills/moai-platform-deployment
Command: npx skills add https://github.com/yekinya/moai-novel --skill moai-platform-deployment-yekinya

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Choosing and configuring a deployment platform involves comparing edge, container, and real-time backend options, then writing correct configuration files, CI/CD pipelines, and environment setups for each. This Skill provides decision guides, ready-to-use configurations, and platform-specific references for Vercel, Railway, and Convex. ## Core Features & Use Cases - Platform Selection Guidance: Decision trees and feature matrices comparing Vercel (edge-first), Railway (container-first), and Convex (real-time backend) by compute, storage, networking, and pricing. - Deployment Configuration: Ready-made vercel.json, railway.toml, multi-stage Dockerfiles, and Convex schema examples with CI/CD workflows for GitHub Actions. - Architecture Patterns: Five common deployment patterns including hybrid edge-plus-container stacks and real-time collaborative app setups. - Use Case: You are building a Next.js app with a real-time chat feature. Use this Skill to deploy the frontend to Vercel, connect a Convex backend for reactive queries, and set up preview deployments via GitHub Actions. ## Quick Start Ask the assistant to help you choose between Vercel, Railway, and Convex for your application and generate the deployment configuration for the selected platform.

Frequently Asked Questions about moai-platform-deployment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose between Vercel, Railway, and Convex for deployment?

Choose Vercel for Next.js apps needing global edge distribution, Railway for containerized multi-service apps with Docker and private networking, and Convex for real-time collaborative backends with reactive queries. The decision tree in the comparison reference walks through requirements step by step.

How do I deploy a Docker container to Railway?

Create a multi-stage Dockerfile, configure railway.toml with the DOCKERFILE builder, health check path, and resource limits, then run railway up. The Railway reference includes optimized Dockerfile patterns for Node.js, Python, and Go.

Does Vercel support WebSocket connections?

Vercel does not support long-lived WebSocket connections on its serverless or edge functions. For WebSockets, deploy the service to Railway, or use Convex which provides real-time sync through its reactive query system instead.

How do I set up preview deployments with GitHub Actions?

Use the amondnet/vercel-action GitHub Action with your Vercel token, org ID, and project ID stored as repository secrets. Vercel automatically creates preview deployments for pull requests; Railway and Convex use CLI-based deploy steps instead.

Can I migrate from Vercel to Railway without rewriting my app?

Yes, if your app can run in a Docker container. Create a Dockerfile, export environment variables with vercel env pull, import them via railway variables, and update DNS records. Serverless-specific features like ISR need alternative implementations.

What are the cold start differences between these platforms?

Vercel Edge functions start in under 50ms, Vercel serverless functions around 200ms, and Convex around 100ms. Railway containers run persistently with no cold starts, making them suitable for latency-sensitive long-running services.