Host an app built with Claude Code: Git and deployment

Claude Code can help create an application in your local project, but the coding agent and the hosting are separate. To put the app on a public URL, inspect the code, choose where it runs and connect a domain. This guide covers Claude Code → Git → Hostbrid without assuming a specific app is compatible until it has been tested.

Anthropic describes Claude Code as a tool that works from the terminal in your development environment. If you mean a Claude Artifact, that is a different flow: you can share the prototype from Claude; when you want to move its code into an editor and prepare your own infrastructure, see our guide to putting an Artifact on your own domain.

1. Check what Claude Code generated

From the project folder, inspect package.json, the README, configuration files and Git status. Identify the framework, the branch with the right version, and the install, build and start commands. Do not blindly paste an agent’s suggested commands into production: confirm they exist and run the project locally.

Separate the files Claude helped create from the services the app still needs. Does it generate static HTML? Start a Node process? Call an API or need a database, login, storage or scheduled jobs? A React site can be static, but a server route or backend action changes the hosting requirement.

2. Protect keys and external services

Look for process.env, import.meta.env, API, OAuth and .env references. Add .env to .gitignore before your first push, and never commit an API key or place one in browser code. Store secrets in the appropriate runtime environment and check which variables the app needs at build time and at startup.

If Claude wrote code that calls an AI provider from React, move the key to the server before publishing. A VITE_* variable is included in the browser bundle; it is not a secret store. Also check provider quotas and costs, CORS, OAuth callback URLs and database access rules.

3. Push the code and choose a destination

Push the project to a Git repository and review the diff and included files first. Hostbrid Projects can connect a repository for deployment; available options depend on the plan and service mode. If the repository only produces static files, Sites may fit. If you need to manage the operating system and containers, consider a VPS; you operate that server.

In Projects, select the production branch and validate the actual install, build and output settings. If the app needs a Node or Docker process, confirm your plan supports the service and configure its port and environment for the application. Claude Code does not connect the repository to Hostbrid, publish a build or automatically configure DNS or HTTPS.

4. Test before pointing the domain

Start with the temporary URL. Open internal routes directly and test forms, authentication, backend calls and writes. Confirm logs contain no secrets and integrations allow the new domain. A successful build does not prove that routes, payments or data work.

After the tests pass, connect the domain and verify HTTPS, redirects and callbacks. Keep the previous deployment available until you have checked the new one. For an app with data, prepare a copy and a restoration plan before changing schemas or moving storage.

Operationally: Claude Code helps produce code; Git versions it; hosting serves or runs it; external services retain their own configuration and costs. Review the current plans and resources before deploying.

Sources: Anthropic Claude Code getting started · Claude Artifacts: prototype to production · Hostbrid Projects