Step 1: identify what kind of app you have
Before you deploy an AI-generated or vibe-coded app, quickly identify the project shape. SiteDropper can help with detection after upload, but knowing the basics helps you choose the fastest path to a live URL.
- Static site: an index.html file, a docs site, or a built front-end bundle.
- Node app: React, Vite, Express, Fastify, Next, Nest, or another JavaScript project with package.json.
- Python app: Flask, FastAPI, Django, or another service with dependency metadata such as requirements.txt.
- Prototype or client demo: a project that does not need a full infrastructure setup yet, but does need a reliable link to share.
Step 2: make sure it runs locally
The fastest deployment is the one that starts from a working local project. Run the app, check the main page, and fix obvious package or build errors before you upload or ask an agent to deploy it.
- For Node projects, run npm install, pnpm install, or yarn install as appropriate.
- Run the normal build command before deploying, such as npm run build, pnpm build, or yarn build.
- Confirm the start command if the app needs a server process.
- List required environment variables so you can add them before the first production-style deployment.
Step 3: choose your SiteDropper deployment path
SiteDropper gives you three ways to go from local project to live URL. Pick the surface that fits how you are already working.
- Use SiteDropper MCP when you want Codex, Claude Code, Cursor, and more to package, upload, deploy, and report back with the live URL.
- Use ZIP upload when you want the simplest browser workflow from the dashboard.
- Use the REST API when a script, CI job, or internal tool should automate the deployment.
Step 4: deploy as draft first
For a first deploy, keep the project in draft or private visibility while you test the link. Open the generated URL, check the home page, click through the app, and review build logs if anything fails.
- Use the operation status to know whether analysis, build, or deploy is still running.
- If a build fails, look for missing dependencies, incorrect scripts, or environment variables that the app expects.
- Once the app works, decide who should see it: just you, a specific team, or the public.
Step 5: share the live URL
When the app is ready, SiteDropper gives you a shareable URL under the SiteDropper app domain. Use it for a stakeholder review, client demo, internal tool preview, or public launch depending on the visibility you choose.