How to take your app from localhost to live

Open the project with your coding assistant and ask it to identify the framework, build command, server code and database. Ask for file names as evidence. A screenshot of a working app cannot tell you which hosting it needs.

A browser-only app can often be served as static files. An app that renders pages on a server, handles private API calls or runs background work needs somewhere to execute that code too. Your database may already live online, even while the screen runs on localhost.

Use your framework's deployment guide and the host's supported runtimes together. A familiar logo is not enough: server code, scheduled jobs and persistent storage have different requirements.

If your builder already offers publishing, start by understanding that route. Moving to a separate host is a choice, not a compulsory graduation ceremony. Check who owns the account, how billing works and how you'll retrieve the code and data.

• Save the code in a private repository you control. Keep secret values out of it.
• Run the project's production build and resolve the first actual error before deploying.
• Create the host's production configuration. Keep private credentials in server-side secrets.
• Connect the production database and apply reviewed schema changes. Know which environment you're changing.
• Deploy to the host's temporary public URL before adding your custom domain.

Open the public URL on your phone using mobile data, with your laptop's development server stopped. Create a fresh account, save something, refresh a deep link and sign out. Check that another account cannot read your private records.

Find the production logs, keep a known working release and write down how to recover if the next update fails. A public URL is the first milestone. A repeatable, understandable release is the softer landing.

Vibe Code Babysitter started as a local React Router app. Its enquiry form needs server-side validation and private email credentials, so uploading only the browser files would have left out an important part. We deployed the app to Cloudflare Workers with the framework integration.

The production build has its own settings: search indexing and email delivery are enabled only in the intended live configuration. Local previews block indexing and preserve enquiries without pretending to send them. The source lives in a private GitHub repository, and the release command builds that production configuration before deploying.

We checked the public domain, mobile layouts and the protected enquiry flow. The lesson is small but useful: choose a home for the whole customer journey, then test the parts a screenshot cannot prove.