How to deploy vibe-coded Replit Agent apps to production in minutes
You built an app with Replit Agent. It runs in the Replit preview. Now you need it on a real URL, with HTTPS, automatic redeployments when you push changes, and infrastructure that does not break when real users hit it.
This article covers how to deploy a Replit Agent app to production on Northflank: connecting your project to GitHub, configuring the build, and getting a live HTTPS URL with automatic redeployments on every push. Replit Agent can build anything, from a static React frontend to a full-stack Next.js app to a Python FastAPI backend, so some steps will depend on what your app actually is.
Replit Agent builds the app. Northflank runs it in production.
- Connect your Replit project to GitHub in the Replit IDE.
- Connect the repository to Northflank, configure the build, and Northflank deploys the app with TLS in under two minutes.
- Every push to GitHub triggers an automatic redeployment on Northflank.
What is Northflank? Northflank is a full-stack cloud platform that deploys Replit Agent apps with production-grade infrastructure: managed databases, secrets management, TLS, CI/CD pipelines, preview environments per pull request, and BYOC into your own cloud. No infrastructure code. No DevOps background required. Sign up to get started or book a demo.
Replit's built-in hosting works well for prototypes and early testing. Moving to Northflank gives you a production deployment with managed databases, secrets management, autoscaling, preview environments per pull request, CI/CD pipelines, and BYOC support when your app grows. You keep building in Replit. Northflank handles everything underneath.
Before connecting to GitHub, ask Replit Agent to generate a Dockerfile for your app. A Dockerfile is the most reliable way to deploy any Replit project on an external platform, regardless of the framework or language. Open the Replit chat and paste this prompt:
Add a Dockerfile to this project so I can deploy it anywhere with Docker.
The agent will generate a Dockerfile specific to your project. For a Node.js app, it will install dependencies, build, and run the server. For a Python app, it will install requirements and start the ASGI or WSGI server. For a Next.js app, it will run the build and start the Next.js server.
Once the agent is done, check two things before moving on:
- The Dockerfile is visible in your project file tree
- Ask the agent: "What port does my app run on in the Dockerfile?" Write this down. You will need it in Step 4.
Confirm both look correct before continuing.
In the Replit IDE, click the + icon at the top to open a new tab, then search for Git and select Git. This opens the Git settings panel. Under Connections, click Sign in next to GitHub. If you do not have a GitHub account, create one for free at github.com before continuing.
Once signed in, click Create Remote in the top right of the panel. Enter a repository name, set the privacy, and click Create Repository on GitHub.
Your project is now connected to GitHub. Every commit you push from Replit will trigger an automatic redeployment on Northflank.
Sign up for Northflank. The free tier includes two services, one database, and two cron jobs with always-on compute.
Once you are in the dashboard, link your git account and create a new project. A project is a container for all the resources that belong to your app: services, databases, secrets, and pipelines.
- Click New project from the dashboard
- Give it a name matching your Replit app
- Choose a deployment target (
Northflank Cloud) - Select a region closest to your users
- Click Create project
- Inside the project, click Create service
- Select Combined service and enter a name, for example
replit-app - Select your repository from the dropdown and choose the branch to deploy from
- Under Build options, select Dockerfile. Northflank automatically detects the Dockerfile if it is in the root of the repository, but Replit Agent may place it in a subdirectory. Ask the agent for the exact path and enter it in the Dockerfile location field, for example,
/artifacts/project-name/Dockerfile. - Under Networking, add a public port. Use the port number Replit Agent told you in Step 1. Northflank provisions a public HTTPS URL on this port automatically
- Under Environment variables, add any credentials or configuration your app needs. There are two types: build arguments are injected during the build process, and runtime variables are injected when the app is running. If you are unsure which to use, ask Replit Agent: "Do my environment variables need to be available at build time or runtime?" Add your variables in the correct section based on the answer
- Leave resources at the default values. You can enable autoscaling from the resources panel at any time
- Click Create service
Tip: If your app has multiple services or you want to manage credentials in one place, secret groups are a better option than adding variables directly to each service.
Northflank builds the app and deploys it. TLS is provisioned automatically. Your Replit app is live on a *.code.run URL in under two minutes.
To use your own domain, first verify it in your Northflank account settings by adding a TXT record to your DNS provider. Once verified, add a subdomain and point it to your service port using the CNAME record Northflank provides. Northflank provisions a TLS certificate automatically.
For the full walkthrough, see Add and verify a domain in the Northflank docs.
By the end of this guide, your Replit app has:
- A live HTTPS URL on a
.code.runsubdomain or your own domain - Automatic redeployment on every push to GitHub
- Environment variables are injected at runtime with no credentials in the source code
- Always-on compute on the free tier
When your app grows beyond a prototype and needs a managed database, background workers, preview environments per pull request, or the ability to run inside your own cloud account, Northflank covers all of it from the same control plane.
No. You keep building in Replit. Every change you push to GitHub from the Version Control tab triggers an automatic redeployment on Northflank. Your workflow stays in Replit. The production infrastructure runs on Northflank.
It depends on your app. For simple frontends and standard runtimes, Northflank's buildpack detection handles the build automatically. For full-stack apps with custom servers, background processes, or multiple services, a Dockerfile gives Northflank precise instructions on how to run your app. Ask Replit Agent to generate one if you are unsure.
Copy the error from the Northflank build logs and paste it into the Replit Agent chat. The agent can diagnose most build failures and suggest the fix, whether that is a missing dependency, a wrong build command, or a Dockerfile configuration issue.
Push your changes to GitHub from the Replit Version Control tab. Northflank detects the new commit and triggers a new build and deploy automatically. No manual steps required after the initial setup.
Yes. Northflank provides managed PostgreSQL, MySQL, MongoDB, Redis, MinIO, and RabbitMQ as first-class addons. Provision one from the project dashboard, and Northflank injects the connection string automatically via secret groups.
Yes. Northflank preview environments spin up an isolated copy of the app per pull request and tear down automatically on merge. For a full walkthrough, see How to auto-create preview environments on every PR.
Replit Agent builds the app. Northflank keeps it running in production. Ask the agent what command starts your app and what port it uses, connect to GitHub, and Northflank does the rest.
Sign up for free and deploy your Replit app in minutes. Or book a demo if you want to walk through your specific setup with an engineer.
- How to deploy vibe-coded apps to production: The general guide for deploying any vibe-coded app on Northflank, with a step-by-step walkthrough.
- How to deploy and host apps built with Lovable to production: The same workflow for Lovable apps, with Lovable-specific steps for GitHub export and Supabase credentials.
- Best deployment platforms for vibe coders in 2026: A comparison of Northflank, Vercel, Render, Railway, and Fly.io on databases, secrets management, preview environments, and full-stack scope.
- How to auto-create preview environments on every PR: Step-by-step guide to setting up automatic preview environments so every pull request gets its own isolated deployment.
