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 with the app.

Create files with the `+api.ts` suffix inside the app directory, such as `app/api/hello+api.ts`. Export named functions like GET or POST that receive a Request and return a Response, and dynamic segments use bracket syntax like `[id]+api.ts`.

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

Use `eas env:create --name KEY --value value --environment production` or the Expo dashboard to create secrets. Locally, place variables in a `.env` file and access them in API routes via `process.env`.

Avoid API routes for public data, real-time updates needing WebSockets, simple CRUD better served by Firebase or Supabase, file uploads suited to presigned URLs, and authentication-only needs covered by Clerk or Auth0.

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.