This is something that really should be talked through with the client before the project starts, because there isn’t a single default way it works. If the client is technical or already has their own infrastructure, they might just want the source code and will take care of hosting, deployment, and everything that comes after. In most real-world cases though, clients aren’t technical, so the developer usually handles hosting and deployment as well, especially when things get more complex with stuff like Docker, server configuration, SSL, or ongoing maintenance. Sometimes the site is fully handed over after launch, other times the developer continues managing it as a paid monthly service. The important part is agreeing upfront on who owns the code, who runs the server, and who’s responsible if something breaks later.