How to Deploy a Replit App to Production with DeployHQ

This guide will walk you through creating a simple web app using Replit's AI Agent and then deploying it to a live server using DeployHQ.

Why Deploy Beyond Replit?

Replit is an excellent environment for building and prototyping. But when it comes to running a production app, hosting it on your own server gives you several advantages:

• Custom domain: Point your own domain at your server rather than using a Replit subdomain
• No vendor lock-in: Your code lives in Git and deploys to infrastructure you control
• Better performance: A dedicated server or VPS typically outperforms shared browser-based hosting for production traffic
• Full control: Configure caching, SSL, server-side logic, and environment variables without platform restrictions

DeployHQ bridges the gap — it connects your Git repository to any server and automates every deployment.

Step 1: Set Up Your Replit Account

First, go to Replit and sign in or create a new account. Replit is a powerful platform that lets you code and run applications directly from your browser. For this guide, we'll use the Replit Agent, an AI tool that helps you build apps quickly.

A note on pricing: Replit uses effort-based pricing for its AI Agent, meaning costs scale with the complexity of each task. Plans range from a free Starter tier to Core ($20/month) and Pro ($100/month for up to 15 builders). Keep this in mind when building larger applications — simple prototypes stay affordable, but complex multi-step builds can consume credits quickly.

Step 2: Start Building with Replit Agent

Once you are logged in, open a new project. In the Replit dashboard, you'll see a prompt box where you can interact with the Replit Agent. For instance, you could type: "Build me a static calculator app in HTML and JS." The Replit AI will take care of the rest. You can make your request more specific by adding details to get a better result. You can also click "Improve prompt" to have the AI expand on your simple idea, which can be very helpful.

Step 3: Let the Replit Agent Think

After you hit "Start Building," the Replit Agent will begin to think about how to create your app. It will plan the best approach before writing any code. You'll then see the app's code come together automatically. The agent is designed to catch and fix bugs on its own, ensuring a smooth build process.

Step 4: Generate the Build Files

After your app is ready, you'll need to prepare it for production. In the Replit IDE, find the Shell terminal and run the build command. For most JavaScript projects, this is npm run build. This command will generate a folder (usually named dist or build) containing all the necessary files for a live site.

Before deploying with DeployHQ, you must first connect your Replit project to a Git repository. In Replit, you can find the Version Control tab (it looks like a Git icon) on the left-hand side. Initialize a Git repository, commit your files, and push them to a service like GitHub, GitLab, or Bitbucket. DeployHQ will deploy from this repository, not directly from Replit.

Step 5: Publish Your App with DeployHQ

Now, instead of using a service like Tiiny.host, you will use DeployHQ to get your app live. DeployHQ is a deployment automation service that works with your Git repository.

1. Create a DeployHQ Project: Go to the DeployHQ website and sign up for an account. Once logged in, click New Project.

2. Connect to Your Git Repository: DeployHQ will prompt you to connect to your Git provider (e.g., GitHub). Give DeployHQ permission to access your repository and select the project you just pushed from Replit.

3. Set Up Your Deployment Server: In your project, navigate to Servers & Groups and click New Server. Choose your connection method (e.g., FTP, SFTP, or SSH) and enter the necessary credentials for your hosting server. You will also specify the deployment path, which is the directory on your server where the files will be uploaded (e.g., /public_html).

4. Initiate the Deployment: Go to the Deployments tab and click New Deployment. Select the branch you want to deploy from (e.g., main or master) and the server you just configured. DeployHQ will automatically compare your repository with the last deployment and transfer only the changed files.

Step 6: Configure Build Pipelines

If your app requires a build step before deployment (such as compiling TypeScript, bundling assets, or running npm run build), DeployHQ can handle this automatically as part of the deployment pipeline — you do not need to commit your compiled output to Git.

In your DeployHQ project, navigate to Build Pipelines and click New Build Pipeline. Here you can define one or more commands to run before files are transferred to your server. For a typical JavaScript project you might add:

npm install
npm run build

You can also set the deployment path to match your build output folder (e.g., dist/ or build/) so that only the compiled files are uploaded to your server, rather than the entire repository. This keeps deployments clean and fast.

Build pipelines run on DeployHQ's infrastructure, so your server only ever receives the finished, production-ready files.

Step 7: Set Up Automatic Deployments

Manually triggering a deployment every time you push code gets tedious quickly. DeployHQ supports automatic deployments via webhooks, so every push to your repository triggers a deployment with no manual steps required.

To enable this, go to your project's Repository settings in DeployHQ and copy the webhook URL provided. Then, in your Git provider (GitHub, GitLab, or Bitbucket), navigate to your repository's webhook settings and paste that URL. Set the trigger to fire on push events for whichever branch you deploy from (typically main).

From this point on, the workflow is fully automated: you push a change from Replit (or any editor) to GitHub, the webhook fires, DeployHQ runs your build pipeline, and the updated files land on your server — all within seconds, with no manual intervention.

Step 8: Monitor Your App

DeployHQ provides a comprehensive dashboard to monitor the status of your deployments. You can see the logs of each deployment, check for any errors, and even roll back to a previous version if something goes wrong. This gives you much more control and insight into your app's lifecycle compared to a simple drag-and-drop service.

If a deployment introduces a bug, the one-click rollback feature lets you restore the previous working version immediately, without needing to revert commits or redeploy manually.

Ready to take your Replit project live? Sign up for DeployHQ and connect your repository in minutes — plans start with a free trial. Check out DeployHQ pricing for details.

Building with other AI tools? See our deployment guides for Lovable, Bolt, and v0. For AI-assisted coding editors, check out our guides for Cursor, Windsurf, and Cline.

If you run into any issues, reach out to the team at support@deployhq.com or on X at @deployhq.