{"slug": "how-to-share-a-claude-artifact-with-your-team", "title": "How to share a Claude artifact with your team", "summary": "Croft published a September 12, 2026 guide arguing that Claude artifacts cannot be shared with a team as-is and must be deployed to a private hosted server with sign-in and a database. Croft prices the service at $24/month for Solo and $99/month for Team on annual billing, with a 7-day free trial and no card required to start. The guide walks through connecting Claude to a Croft private server, asking Claude to deploy the artifact as an app, and inviting teammates to open a normal URL and sign in.", "body_md": "[Blog](https://oncroft.net/blog/) · September 12, 2026 · Rich Chetwynd\n\n# How to share a Claude artifact with your team\n\nA Claude artifact lives in your chat. Emailing the HTML is not a real share. Here is how to host it so your team can open it like a normal app.\n\n## Quick answer\n\nIf you built something useful in Claude (a financial model, a calculator, a\ntracker) and the only way to share it is pasting HTML or screenshots, you need\nto **host it as a real app**. Put it on a private server, give it a URL your\npeople can open, and let them sign in. That is what Croft is for. You do not\nneed to know how to code or manage servers.\n\n## The problem with “just share the artifact”\n\nClaude Artifacts (and ChatGPT Canvas, and similar previews) are brilliant for building in the moment. They are a poor way to run a tool for a team:\n\n- The preview lives in **your** chat. Colleagues cannot open it on their own.\n- There is usually **no lasting database** . Numbers vanish when the session\nends.\n- Emailing an `.html` file means every person has a different copy, nothing is\nsaved together, and updates mean another attachment.\n- A public paste or public host puts internal numbers on the open internet unless you invent login yourself.\n\nSo the model worked. The sharing step failed.\n\n## What “host my AI app” should mean\n\nFor a business tool, hosting is not “get any live URL.” It is:\n\n1. A **link the team can open** in a browser\n2. **Sign-in for your people** , so strangers cannot wander in\n3. A **database** so the model remembers inputs and results\n4. **Backups and a way to undo** a bad change\n5. A path to **update by chatting** again, without starting from zero\n\nIf you do not care about coding, the host should handle the dull parts: HTTPS, deploys, and keeping the server online.\n\n## Artifact vs hosted app\n\n| Need | Claude artifact | Email the HTML | Public host | Croft | \n|---|---|---|---|---|\n| Team can open their own link | No | Fragile copies | Yes | Yes | \n| Shared saved data | No | No | Extra setup | Included | \n| Private to your people | Chat-only | File chaos | You build login | Built in | \n| No devops required | N/A | N/A | Sometimes | Yes | \n| Keep iterating with AI | In chat only | Start over | Varies | Connect Claude and keep going | \n\n## How to get there with Croft\n\n1. Get a croft (private server) and connect [Claude](https://oncroft.net/connect/claude/) , or use[Croft Build](https://oncroft.net/build/) if you prefer not to connect an assistant yet.\n2. Ask Claude to **deploy the artifact to your croft** as an app.\n3. Invite the people who should use it. They open a normal URL and sign in.\n4. Keep chatting to change the app. Deploys and rollbacks stay on the server.\n\nMore on the product path: [From artifact to app](https://oncroft.net/artifacts/).\n\nYou still do not need to learn nginx, Docker, or “how to deploy.” The point of Croft is that the assistant can ship it for you.\n\n## FAQ\n\n### Can I just send the HTML file?\n\nYou can, once. Then someone edits a number, another person has an old copy, and nobody has a shared source of truth. That is fine for a demo. It is not fine for a financial model your team uses every week.\n\n### Do I need to be technical?\n\nNo. If you can chat with Claude, you can ask it to deploy to Croft. The people who get the most from this are subject-matter experts (finance, ops, sales), not platform engineers.\n\n### Is this the same as putting it on Vercel or Replit?\n\nThose are strong for public products. For an internal model or tracker, you\nusually want a private server and team sign-in by default, not a public URL you\nmust lock down after the fact. See also\n[Where to host a vibe-coded app so it stays private](https://oncroft.net/blog/where-to-host-a-vibe-coded-app-privately/).\n\n### What about ChatGPT Canvas or other previews?\n\nSame job. A preview in chat is not a team app. Deploy it to Croft when you want a lasting URL, saved data, and people you invite.\n\n### How much does Croft cost?\n\nSolo from $24/month on annual billing, Team $99/month on annual. 7-day free trial, no card to start.\n\n## Stake out your croft.\n\nYour team's first app could be live before lunch.\n\n[Get your croft](https://app.oncroft.net/signup)\n\n7 days free, no card to start. From $24/month - cancel anytime and take everything with you.", "url": "https://wpnews.pro/news/how-to-share-a-claude-artifact-with-your-team", "canonical_source": "https://oncroft.net/blog/share-claude-artifact-with-your-team/", "published_at": "2026-09-11 12:00:00+00:00", "updated_at": "2026-09-24 04:28:58.733910+00:00", "lang": "en", "topics": ["ai-tools", "ai-products", "generative-ai"], "entities": ["Croft", "Claude", "Anthropic", "ChatGPT Canvas", "OpenAI", "Vercel", "Replit", "Rich Chetwynd"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/how-to-share-a-claude-artifact-with-your-team", "markdown": "https://wpnews.pro/news/how-to-share-a-claude-artifact-with-your-team.md", "text": "https://wpnews.pro/news/how-to-share-a-claude-artifact-with-your-team.txt", "jsonld": "https://wpnews.pro/news/how-to-share-a-claude-artifact-with-your-team.jsonld"}}