The short answer: zip your Claude Code project, upload it to VibeHub, and it goes live on a private URL behind your company's login — usually in a few minutes. No Dockerfile, no cloud account, no CLI.

The problem

Claude Code is one of the fastest ways to build a real internal tool — a dashboard, a data cleaner, an approvals app. But unlike browser builders such as Lovable or Bolt, Claude Code has no built-in "share with my team" button. Your app works on localhost:3000, and then you hit the wall every CLI-agent builder hits:

  • You don't want to stand up and babysit a Vercel/Fly/AWS deployment for a tool three people use.
  • You definitely don't want it public — it probably talks to a spreadsheet, a database, or a CRM.
  • Emailing the repo around or screen-sharing the app defeats the point.

Deploying to VibeHub, step by step

  1. Build the tool as usual. VibeHub runs static sites, Next.js apps, and Streamlit apps, so tell Claude Code to use one of those. A useful prompt addition: "Build this as a Next.js app. Read all configuration and API keys from environment variables."
  2. Zip the project. The project folder as-is — node_modules isn't needed; VibeHub installs dependencies during its build.
  3. Upload it in the VibeHub dashboard. Create an app in your workspace, drop the zip, and VibeHub detects the framework, builds it, and deploys it to an isolated runtime.
  4. Set secrets. API keys, database URLs — anything the app reads from process.env (or os.environ for Streamlit) goes into the app's secrets settings, encrypted, outside the code.
  5. Share the URL. Teammates open the app's address and sign in with your workspace login. Nobody outside your workspace can reach it — the gateway checks identity before a single byte of your app is served.

What you get that a raw deploy doesn't give you

Deploying the zip is the easy half. The reason to put a work tool on VibeHub instead of a personal Vercel account is everything after day one:

  • Private by architecture. Apps live behind an identity gateway on isolated origins. There is no "forgot to enable auth" failure mode.
  • Rollback. Every upload is a version; if v4 breaks the tool during a workday, restore v3 in one click.
  • Kill switch. If an app misbehaves — or you just discover it's holding credentials it shouldn't — turn it off instantly for everyone.
  • Audit log. Who accessed the tool, who changed it, who changed its secrets. The answer to "wait, who deployed this?" is written down.
  • Survives the builder. When the person who prompted the tool into existence changes teams, the app, its versions, and its secrets stay in the company workspace.

When you don't need this

If the tool is for you alone, localhost is fine. If it's a public side project, a normal hosting platform is the right tool. VibeHub is for the middle case — the app is internal, more than one person needs it, and it touches anything you wouldn't post publicly.