# Deployment

Once you have your application working and ready to be deployed you can create a production version by running (from the root of your project)

```
npx frontity build
```

This command will [generate a `build` folder](https://api.frontity.org/frontity-cli/build-commands#the-build-process) containing both your (isomorphic) React app and your Frontity (Node.js) server. This folder can be deployed to any hosting that is prepared to serve a Node.js app. The content of this `build` folder will be used by the command:

```
npx frontity serve
```

Which is used to launch the Frontity app in production.

Here you have some guides about how to deploy a Frontity app in some popular hostings:

* [Deploy Frontity using Vercel](/deployment/deploy-using-vercel.md)
* [Deploy Frontity on Layer0](/deployment/deploy-on-layer0.md)
* [Deploy Frontity on Heroku](/deployment/deploy-on-heroku.md)

## Serving Static files

Sometimes you will want to serve your assets (also called "static files" like images, fonts, JS chunk files) from another domain or from a [CDN](/performance/caching.md#distributed-caching-cdn). In this case, you can modify the [`publicPath` parameter](/deployment.md) when you run `npx frontity build`.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook-docs.frontity.org/deployment.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
