What is the safest way to share an app you built with Claude?
It depends on two things: whether everyone who needs the tool has a Claude account, and whether the tool has to keep records. If they all have accounts and it only stores a little text (artifacts hold up to 20 MB of text), share it as a Claude artifact with named people or your organization, not with an open link. If some colleagues don't have Claude, or the records must last and be backed up, put it on a host that gives the app its own sign-in and database.
Updated 7 November 2026.
Who can open what
| Question | Artifact shared with your organization or named people | Artifact shared by link | App on a host with its own sign-in and database |
|---|---|---|---|
| Needs a Claude account to open | Yes. Invitees need a Claude account with the invited address | Depends on the plan and settings, and parts that use Claude or connected apps don't work for outside viewers | No. On Haechy, colleagues use an emailed one-time link |
| What it can keep | Text only, 20 MB per artifact | Same | A database per app, backed up nightly on Haechy |
| Backups | Not documented by Anthropic | Same | Nightly on Haechy; ask Claude to restore |
| Who can change stored data | People inside the organization. Outside people can read it after signing in to Claude but can't change it | Same limits for outside viewers | Everyone you let in, as the app allows |
| Where the data is stored | Anthropic doesn't document a region choice for artifacts | Same | The region you choose, on Haechy: US, EU, UK or Australia |
As documented by Anthropic on 7 November 2026: sharing artifacts, artifact storage, artifacts in Claude Code. Their pages change, so check them for the latest.
On Team and Enterprise plans artifacts stay inside your organization by default, and email invitations (in beta) allow up to 50 outside people per artifact. The longer side-by-side is in Haechy or a Claude artifact for a team app?
Anthropic describes an artifact as one self-contained page with no backend that can't authenticate viewers itself, and suggests deploying a hosted internal tool with a backend on your own infrastructure instead. That is a fair reading of the job: an artifact is a very good way to share a page or a small tool among people who already use Claude.
Which one for which situation
Say your finance team of six all have Claude on a work plan, and the tool is a calculator that doesn't need to remember anything. Share the artifact with the organization. Nothing else is needed.
Say you made an expense tracker and half the people who should use it have never opened Claude. Their entries also need to be there next month. An artifact can't give them a sign-in without a Claude account, and 20 MB of text is small for a year of claims. This is the case for a hosted app.
Say the tool is a team checklist of a few hundred lines. A shared artifact with shared storage is probably enough, and it is the easier thing to run.
Say the tool will have customers or suppliers filling something in. Invited artifact viewers outside your organization need a Claude account too. A hosted app lets you add people by email, and on paid plans a page can also be public.
If the data is sensitive
For finance or HR data, the useful questions are about controls you can check, and no tool can promise safety:
- Who can open it, and does every visitor have to sign in?
- Where is the stored data kept, and in which region?
- Who can see it on the provider's side? Haechy, for one, says plainly that its staff can technically reach customer data on its servers and that it makes no claim it can't be breached.
- Can the app call outside services on its own, or does a person approve each one first?
- What happens after a mistake: is there a backup, and can you restore it?
Those questions apply to an artifact, to Haechy and to anything else. If your IT team has a say, the page for IT teams lists what Haechy does and doesn't do in their terms.
Where Haechy fits
Haechy is one host in that last column. You ask Claude to build the app and put it online, and Haechy runs it at its own address (yourname.haechy.app) with a Postgres database, nightly backups and sign-in in front of every page. Colleagues you add by email get a one-time sign-in link: it works once, expires after 15 minutes, and keeps their browser signed in for 12 hours. They need no password, no Haechy account and no Claude account. Any outside service the app wants to reach waits until you approve it, and Claude can't approve it for you.
The free plan gives you 2 apps and 5 people who can sign in (you count as one), with no card. Paid plans are listed on the pricing page, and checkout isn't open yet. Haechy's limits are real: free apps sleep after 15 minutes without use, and the terms promise no uptime guarantee. It isn't built for public marketing sites. Steps for connecting it are in the Claude setup guide, and the quickstart covers the first app. Other hosts at the same level exist; this list compares them.
Your app, its database, its backups and uploaded code are stored in the region you choose. Some services we use to send email, verify phone numbers and take payments process data outside your chosen region. See our sub-processors. Your Haechy account and sign-in records run on a control plane in the US.
Can I share it with a customer?
With an artifact, only if they have a Claude account, and what they can do is limited. With a hosted app, add their email and they get the same sign-in link as a colleague, within your plan's people limit. Giving colleagues access without accounts goes through the sign-in choices.