eas-hosting

Export the web bundle with npx expo export -p web, then run npx eas-cli@latest deploy for a preview URL or add --prod for production. The same command deploys any Expo Router API routes bundled alongside the site.

Create files with the +api.ts suffix inside the app directory, such as app/api/hello+api.ts, and export named functions for each HTTP method like GET or POST. Dynamic segments use bracket syntax like app/api/users/[id]+api.ts.

No, API routes run on Cloudflare Workers, so the Node.js filesystem and native modules are unavailable. Use Web APIs like fetch, crypto.subtle, Request, and Response instead, and connect to cloud databases such as Turso, Supabase, or Neon.

Use eas env:create with the name, value, and environment flags, or configure secrets through the Expo dashboard. Locally, place variables in a .env file that is never committed, and access them in routes via process.env.

Avoid API routes for public data, real-time updates, simple CRUD, file uploads, or authentication-only needs. Use Supabase Realtime, Firebase, direct-to-storage uploads, or dedicated auth providers like Clerk or Auth0 instead.

EAS Hosting is a paid Expo Application Services product with free-tier limits, and production deploys consume your plan's request and bandwidth allowance. Authoring API routes and exporting the web bundle are free, and you can self-host the exported output instead.