Overview
Launch is designed for easy deployment to production. This section covers deploying both your backend API and mobile app. Most of the mobile workflow is handled by Expo (EAS Build + EAS Submit), so deployment can be completed in a single afternoon once your backend is live.Backend to Railway
Deploy your API to Railway in minutes.
Mobile with EAS
Build and distribute with Expo Application Services.
If you need Docker or advanced env management, use the official Railway docs
or your platform’s deployment guides.
Prerequisites
- A production database
- A hosting provider for the API
- Apple/Google developer accounts (if submitting to stores)
Steps
- Deploy the API (Railway or your provider)
- Set production env vars (API + mobile)
- Build mobile binaries with EAS
- Submit to the stores
Deployment Checklist
Before deploying to production, ensure you’ve completed:Require the integrations you use
In
apps/api/src/config/env.ts, update any integration env vars you rely on
(Stripe, Apple, Google, Twilio, push, AWS, etc.) from optional to required
so the API fails fast if a value is missing.Security Review
Completed security checklist
Quick Links
| Platform | Time | Difficulty |
|---|---|---|
| Railway (Backend) | 10 min | Easy |
| EAS Build (Mobile) | 15 min | Easy |
| EAS Submit | 20 min | Medium |
First time deploying? Start with
Backend to Railway - it’s the fastest way to
get your API live.
Troubleshooting
- Env missing at runtime: verify variables in your host (Railway/EAS)
- Mobile can’t reach API: confirm
EXPO_PUBLIC_API_URL