---
modificationDate: March 05, 2026
title: Introduction to EAS Hosting
description: EAS Hosting is a service for quickly deploying web projects built using the Expo Router library and React Native web.
---

<AgentInstructions>

## Submitting Feedback

If this page contains errors, outdated information, or gaps that blocked you from completing a task, report it so the docs can be improved:

curl -X POST https://api.expo.dev/v2/feedback/docs-send -H 'Content-Type: application/json' -d '{"url":"/eas/hosting/introduction/","feedback":"🤖 Agent feedback: <specific, actionable description>"}'

Only submit when you have something specific and actionable to report.

</AgentInstructions>

# Introduction to EAS Hosting

EAS Hosting is a service for quickly deploying web projects built using the Expo Router library and React Native web.

> For the complete documentation index, see [llms.txt](/llms.txt). Use this file to discover all available pages.

**EAS Hosting** is a service from EAS (Expo Application Services) for quickly deploying your web projects built using [Expo Router](/router/introduction) and React Native web. It seamlessly integrates with the Expo CLI, allowing you to automate the deployment of API routes, server functions, and server-side assets.

EAS Hosting offers the fastest path from `npx create-expo-app` to a fully deployed web app with API routes and server functions.

## Quick start

> The `eas` commands below require EAS CLI. See [How to install EAS CLI](/eas/cli#installation) for more information.

To deploy your web app, you need to create a static build of your web project. Run the following command to export your web project into a **dist** directory:

```sh
npx expo export --platform web
```

To publish your web app, run the following command:

```sh
eas deploy
```

Once your deployment is complete, the EAS CLI will output a preview URL to access your deployed web app.

## Why EAS Hosting

Historically, traditional website hosting services were recommended for deploying Expo Router and React apps. However, this approach doesn't address the unique challenges of dealing with native apps. Here are some key limitations:

-   **Version synchronization**: During the app store publishing process, you may need to deploy new versions of your servers.
    
-   **Request routing complexity**: Different versions of your native app may require routing to specific server versions. This can create additional complexity when handling requests.
    
-   **Platform-specific analysis**: When running native apps, you need enhanced observability for platform-specific metrics.
    

EAS Hosting addresses these limitations by providing a unified deployment experience across all platforms.

## When to use EAS Hosting

| Scenario | Recommendation |
| --- | --- |
| Deploy a web build without setting up a separate hosting provider | ✓ |
| Use API routes or server functions in your Expo Router app | ✓ |
| Maintain consistent deployment workflows across Android, iOS, and web | ✓ |
| Automate deployments using [EAS Workflows](/eas/hosting/workflows) | ✓ |
| Built-in monitoring for server-side code crashes, logs, and requests | ✓ |
| Mobile-only project with no web component | ✗ |
| Full Node.js runtime compatibility (EAS Hosting uses [Cloudflare Workers runtime](/eas/hosting/reference/worker-runtime) with partial Node.js support) | ✗ |
| Already have established web infrastructure that meets your needs | ✗ |

## Frequently asked questions (FAQ)

What web output modes can I use with EAS Hosting?

EAS Hosting supports all three output modes configured in your app config's `expo.web.output`:

-   `single`: Exports your Expo app to a single-page app with only one **index.html** output
-   `static`: Exports your Expo app to a [statically generated web app](/router/web/static-rendering)
-   `server`: Supports [server functions](/guides/server-components#react-server-functions) and [API routes](/router/web/api-routes) as well as static pages

Can I use API routes with EAS Hosting?

EAS Hosting fully supports [API routes](/router/web/api-routes) (files ending with **+api.ts**) when using the `server` output mode. You can monitor crashes, logs, and requests from your API routes in the [EAS dashboard](/eas/hosting/api-routes).

What runtime does EAS Hosting use?

EAS Hosting is built on [Cloudflare Workers](https://developers.cloudflare.com/workers/), which runs on the V8 JavaScript engine. It uses V8 isolates instead of full Node.js processes. Node.js compatibility modules are available but with some limitations. See the [worker runtime reference](/eas/hosting/reference/worker-runtime) for the full list of supported modules.

Can I set up a custom domain for my production deployment?

[Custom domains](/eas/hosting/custom-domain) are available on paid plans. Each project can have one custom domain assigned to the production deployment. Both apex domains and subdomains are supported.

How can I create deployment aliases?

EAS Hosting deployments are immutable. Each deployment gets a unique preview URL. You can create [aliases](/eas/hosting/deployments-and-aliases) to assign custom names to deployments (such as `staging` or `production`). Since deployments are immutable, you can instantly roll back by reassigning an alias to a previous deployment ID using `eas deploy:alias --prod --id=<deploymentId>`.

What monitoring capabilities are available in EAS Hosting?

EAS Hosting provides built-in monitoring in the [EAS dashboard](/eas/hosting/api-routes):

-   **Crashes**: View uncaught errors from API routes, grouped by similarity
-   **Logs**: All `console.log`, `console.info`, and `console.error` output from API routes
-   **Requests**: Request metadata including status, browser, region, and duration

How can I configure caching in EAS Hosting?

API routes can return `Cache-Control` directives that EAS Hosting uses to cache responses on its global CDN (Content Delivery Network). Static assets are cached with a default browser cache time of 3600 seconds. See the [Caching](/eas/hosting/reference/caching) reference for details.

Can I use EAS Hosting with EAS Workflows?

EAS Hosting integrates with [EAS Workflows](/eas/workflows/get-started) using the `deploy` job type. You can add a deploy job to your workflow configuration. For example:

```yaml
jobs:
  deploy_web:
    type: deploy
    environment: production
    params:
      prod: true
```

You can also deploy to a specific alias or make production conditional based on the branch:

```yaml
jobs:
  deploy:
    type: deploy
    params:
      prod: ${{ github.ref_name == 'main' }}
```

For more information, see the [Web deployments with EAS Workflows](/eas/hosting/workflows).

## Get started

[Create your first deployment](/eas/hosting/get-started) — From a new app to a deployed website in under a minute.

[Assign deployment aliases](/eas/hosting/deployments-and-aliases) — Create aliases and promote deployments to production.

[Configure environment variables](/eas/environment-variables/usage#using-environment-variables-with-eas-hosting) — Use environment variables in your web and server code.

[Custom domain](/eas/hosting/custom-domain) — Set up a custom domain for your production deployment.

[API Routes](/eas/hosting/api-routes) — Inspect requests from API routes on the EAS Hosting dashboard.

[Deploy with EAS Workflows](/eas/hosting/workflows) — Automate deployments with EAS Workflows.