How to deploy a vibe-coded app
You vibe-coded an app that works in the chat. Here is how to deploy it, share it and keep it safe without learning DevOps.
Vibe coding gets you a working prototype in an hour. Deploying it is a separate job: a start command, a port, secrets and a decision about who can open it.
What changes between the prototype and a deployed app
- It must start with one command and listen on the port it is given.
- Dependencies must be listed in a file (requirements.txt, package.json) so the host can install them.
- Keys and passwords must come from environment variables, not the code.
- Data must live in a sheet or database, because the app’s own disk is not permanent.
Ask your assistant for a deployable project
Make this project deployable: one start command that reads PORT, a dependency file with pinned versions, every key read from environment variables, and no data saved to local files. List each variable you read.
Deploy it
- Upload the folder, a .zip or a GitHub repo, or ask your assistant to deploy it over MCP. Cohostly shows draft settings first, and nothing goes live until you confirm.
- Review the proposed start command, memory and environment variables.
- Add secrets on the private secrets page.
- Open the link yourself first, then share it.
The part people skip
Check the logs once, decide who can open the app, and require approval for edits so a late-night change cannot break it for everyone.
Questions
Do I need to know DevOps to deploy a vibe-coded app?
No. Cohostly reads the project and proposes the settings; you confirm them.
Is a vibe-coded app safe to put online?
Only after secrets are out of the code and access is limited. See the security checklist for AI-generated code.
What if the deploy fails?
Read the logs, or let your assistant read them over MCP and fix the code, then deploy again.