1d:T4bf,---------------------- Wasp apps, which consist of a Node.js server, a static client, and a PostgreSQL database, can be deployed anywhere where you can usually deploy Node.js apps or static apps. For example, you can deploy your server on **Fly.io** () [^1^]. However, Netlify is typically suggested for deploying the client part of your Wasp app, not the server [^2^][^3^]. If your desired provider isn't on the list, you can still deploy your app. It just means there isn't a step-by-step guide available yet. You can also contribute by writing a guide yourself [^1^]. For automated deployment, Wasp currently supports Fly.io and has plans to support Railway soon [^4^]. **^1^]: [Deploying Manually** () **^2^]: [Deployment Overview** () **^3^]: [Deploy to a Fly.io App** () **^4^]: [Deploying with the Wasp CLI** () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------1e:T484,---------------------- Yes, you can deploy on Netlify, but it's typically used for deploying the client (frontend) part of your Wasp app, not the server (backend) [^1^][^2^]. The frontend of a Wasp app is a bunch of static files, which can be deployed to any static hosting provider like Netlify [^3^]. Here are the steps to build the web app for deployment: ```bash cd .wasp/build/web-app npm install && REACT_APP_API_URL= npm run build ``` Replace `` with the URL of the Wasp server that you previously deployed. This command will build the web client and put it in the `build/` directory in the `web-app` directory [^3^]. **^1^]: [Deployment Overview** () **^2^]: [Deploy to a Fly.io App** () **^3^]: [Deploying the Web Client (frontend)** () ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------1f:T53a,---------------------- Netlify is primarily a static site hosting provider and does not support server-side applications like the server part of a Wasp app, which is a Node.js application. Therefore, you cannot deploy the server part of a Wasp app on Netlify. However, there are several other providers where you can deploy the server part of your Wasp app: 1. **Fly.io** (): Fly.io is a hosting provider that supports both the server and database parts of a Wasp app [^1^]. 2. **Heroku** (): Heroku is another provider where you can run the server and PostgreSQL database completely for free [^2^]. 3. **Railway** (): Railway is a provider that supports the server, client, and database parts of a Wasp app [^1^]. 4. **Google Cloud Platform (GCP)** (): GCP is mentioned in a community discussion as a potential place to deploy, but it's noted that it has cold start issues [^3^]. 5. **Azure** (): Azure is also mentioned in the community discussion as a potential place to deploy, especially for its multi-container support and lack of cold start issues [^3^]. Remember, you can deploy each part of a Wasp app (client, server, database) anywhere where you can usually deploy Node.js apps or static apps [^4^].20:T415,---------------------- Netlify is primarily a static site hosting provider, which means it's designed to host static files for the frontend of your web application. It does not support server-side applications like the server part of a Wasp app, which is a Node.js application. If you try to deploy the server part of a Wasp app on Netlify, it simply won

Other places to deploy server

Similar Threads

Similar Threads

Similar Threads