domains / families / devops / eas-hosting

eas-hosting

authentic

Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs, manage environment secrets and custom domains, and work within the Cloudflare Workers runtime. Also covers authoring API routes (+api.ts handlers, HTTP methods, request handling, CORS). Use when deploying an Expo web app or API routes, setting up EAS Hosting, or configuring hosting environments and domains. Not for native builds or store releases - use the eas-app-stores skill for those.

When to use

• **Server-side secrets** — API keys, database credentials, or tokens that must never reach the client
• **Database operations** — Direct database queries that shouldn't be exposed
• **Third-party API proxies** — Hide API keys when calling external services (OpenAI, Stripe, etc.)
• **Server-side validation** — Validate data before database writes
• **Webhook endpoints** — Receive callbacks from services like Stripe or GitHub
• **Rate limiting** — Control access at the server level
• **Heavy computation** — Offload processing that would be slow on mobile

When not to use

• **Data is already public** — Use direct fetch to public APIs instead
• **No secrets required** — Static data or client-safe operations
• **Real-time updates needed** — Use WebSockets or services like Supabase Realtime
• **Simple CRUD** — Consider Firebase, Supabase, or Convex for managed backends
• **File uploads** — Use direct-to-storage uploads (S3 presigned URLs, Cloudflare R2)
• **Authentication only** — Use Clerk, Auth0, or Firebase Auth instead

Skill page

Source