Web Hosting

You might say

Confirm that this project has hosting that can continuously serve the site, then deploy it publicly. Do not treat localhost as live.

A service that continuously stores and serves website files or a running environmentA page that works locally still needs a public environment that can serve it continuously. Web hosting provides that environment for files or a running service; deployment is the one-time action of publishing a version into it. They are related but not the same.

Know first

Deployment Domain DNS

Hosting

Who keeps serving the site after deployment ends

Local projectsite/localhost:3000

→

Deployment · one actionNot published

→

Hosting · ongoing environmentWaiting for a versionexample.com

Deployment sends a version there; the hosting environment keeps serving user requests afterward.

What hosting and deployment each do

Hosting is the persistent environment: It stores static files or keeps a request-serving service running. When people use a public address, the environment returns the page or service result.

Deployment is the action that puts a version there: A deployment publishes one build or code version into the hosting environment. A successful build or a domain alone does not prove the public site serves the right version.

You can say this to an AI Agent

First confirm whether this project needs static file hosting or a continuously running service, then deploy it to the matching hosting environment. Request the page through its public URL and verify the new version rather than localhost; if it is still old, separate a hosting-environment issue from a deployment-version issue.

Learn next

1Deployment→2Domain→3DNS→

Recommended tool

Web fine-tuning tool · Selector Pro

Select page elements for precise AI edits

Click a button, text, or card, note the change, then copy its exact location to AI.

Open Selector Pro website

The platform has assigned a runtime environment, but the public page still shows the old version. What should you check first?

A. Create another hosting environment and have both serve the pageB. Change DNS only because the domain determines which version is servedC. Check whether the latest deployment published the right version, then inspect the public URL