Sharing guide

How to share what you built with Claude Code with your team

Deploy it. Sending the folder, a zip or a localhost link gives your coworkers a copy or a dead link, not a tool they can open every day. A deployed app lives at one permanent address, updates every time Claude Code changes something, and you decide who can open it. On White Ghost that takes one command and the assistant does the rest.

The three ways to share, honestly

WayWhat your team getsWhat breaks
The folder or a zipA copy of the code they have to run themselvesEveryone needs the tools installed; every change means sending it again; no shared data
A localhost or tunnel linkA window into the app on your laptopDies when your computer sleeps; the free tunnel URL changes on restart; anyone with the URL gets in
A deployed appOne permanent URL, one database, one place to updateMost platforms expect Git, a terminal and build settings. White Ghost is the one built for the person who has none of that

Who can open it: the three access modes

  • Public. Anyone with the link.
  • A shared invite code. People need a code you hand them. It is one code for everyone, not a list of named guests, so treat it like a shared password.
  • Your own sign-in. The app asks for a login you write into it, for example with Claude Code's help. This is the mode for "only people at my company".

The mode is part of the app's code, so changing it later means editing and redeploying rather than flipping a switch. Viewers never need an account on any AI platform.

From your laptop to your team, in four steps

  1. Create the app. In the folder Claude Code has been working in, run ghosty init. It creates a repository in your own GitHub account and registers the app. You need a GitHub account; that is where your code lives, so it stays yours.
  2. Hand the rest to the assistant. Every White Ghost app has Open in Claude Code and Open in Codex buttons, plus Copy the instructions: a ready prompt with the app URL and the repository URL. Paste it and Claude Code moves the project into place, adds the access mode you chose, and pushes.
  3. Every push goes live. No separate publish step. Real builds on a full app have taken 53 seconds and 1 minute 27 seconds. ghosty rollback, or the Redeploy button on any earlier build, puts the previous version back.
  4. Send one link. The app's URL is permanent. If you own a domain, point it at the app and the certificate is issued and renewed for you. When Claude Code changes something, push again and everyone sees the new version at the same address.

What your team's tool gets for free

A managed PostgreSQL database (so everyone works on the same data, not on copies), file storage that is added when your code needs it, secrets you paste once in the console and never in the code, integrations with services like Slack, Stripe or OpenAI without pasting API keys, scheduled jobs, analytics with requests and errors per day, and a preview URL for every open pull request so you can check a change before it ships.

Honest limits

  • White Ghost runs Node and Python apps. A single HTML file goes inside a small web app; Claude Code does that in minutes.
  • The app scales to zero when idle, so the first visit after a quiet period takes a moment to wake up.
  • The shared invite code is not a guest list: there is no per-person revocation. If that matters, use your own sign-in.
  • Preview links for pull requests are public URLs; keep production data out of previews.

Questions people actually ask

How do I share a Claude artifact with my team so they can use it every day without a Claude account?

Turn it into a deployed app instead of a shared artifact. An artifact link is a snapshot inside the AI product; a deployed app is a normal website. On White Ghost you run ghosty init, let Claude Code move the artifact's code into the app and push it, and your team opens it at a permanent URL without any Claude account. You choose whether it is public, behind a shared invite code, or behind a sign-in you build in.

I made a dashboard with Claude Code for my team. How do I share it so only people at my company can open it?

Deploy it with an access mode. On White Ghost the honest answer for "only people at my company" is your own sign-in: the app asks for a login you write into it, with Claude Code's help. A shared invite code is simpler but it is one code for everyone, so treat it like a shared password.

How do I put a tool I built with AI online with a password so only my team can see it?

Choose the shared invite code mode when you create the app on White Ghost: everyone who opens the link is asked for the code you hand them. It is one code for the whole team, not per-person passwords. For named accounts, use the own sign-in mode instead.

What is the simplest way to publish a small internal app made with Claude Code without learning Git or servers?

Run ghosty init in the project folder and hand the rest to Claude Code through the Open in Claude Code button. You type one command; the assistant creates the repository, pushes, and the app goes live at a permanent URL. You do need a GitHub account, because the code is stored there and stays yours.

Does my team need a Claude account or any AI account to use the app?

No. A deployed White Ghost app is a normal website at a normal URL. The only thing they may need is the invite code or the sign-in you chose.

Your team deserves a tool, not a copy of one.

Individual builders can start right away. Beta access is free.

Join the beta