# Guides and comparisons

> How to share Claude artifacts and what your AI agents produce, see who opened them, and how Outbox compares to Claude Artifacts, Derive, Display.dev and others.

How to keep what your agents produce stored, organized and ready to share, and how Outbox compares to the alternatives.

## Guides

- [Connect Claude to Outbox (remote connector or npx)](https://out-box.dev/en/guides/connect-claude-to-outbox): Two ways to let Claude publish to Outbox: add the remote connector at mcp.out-box.dev with a browser sign-in, or run the local MCP server with npx and an API key.
- [How to share a Claude artifact with a password](https://out-box.dev/en/guides/share-claude-artifact-with-password): Claude can't password-protect an artifact's public link. Here's how to publish it on Outbox with a passphrase, an expiration date and the option to revoke it.
- [A DocSend alternative for AI-generated proposals and decks](https://out-box.dev/en/guides/docsend-alternative-for-ai-generated-proposals): Your agents already write proposals, decks and technical docs in HTML. Send them to clients as live, password-protected links you can keep polishing after you hit send.
- [How to publish the HTML your agent generates (Claude Code, Cursor, Codex)](https://out-box.dev/en/guides/publish-html-from-claude-code-cursor-codex): Have Claude Code, Cursor, Codex or any agent publish HTML pages to their own URL, private by default and versioned, with the Outbox API.
- [Where to keep the reports and pages your AI agents generate](https://out-box.dev/en/guides/where-to-store-ai-agent-output): Your agents' output gets lost in chats and local folders. Keep it in a private library with URLs, folders, version history and daily documents.
- [How to share Claude artifacts: every option, and when you need more](https://out-box.dev/en/guides/how-to-share-claude-artifacts): Share a Claude artifact privately, with your org or by public link, plan by plan. Plus what Claude can't do (password, expiry, who opened it) and how to add it.
- [How to see who opened your Claude artifact](https://out-box.dev/en/guides/see-who-opened-your-claude-artifact): Claude doesn't show who opened a shared artifact. How to get a per-person link that records each open by name and emails you when your client opens it.
- [Claude artifact not working for others? 9 causes and fixes](https://out-box.dev/en/guides/claude-artifact-not-working-for-others): Your shared Claude artifact opens for you but not for them: org-only sharing, sign-in, External sharing off, unpublished, connectors. Causes and fixes, sourced.
- [How to share Claude Code artifacts outside your organization](https://out-box.dev/en/guides/share-claude-code-artifacts-outside-your-org): Claude Code artifacts stay inside your org unless an Owner enables public links. How to send that HTML to a client with a private per-person link instead.

## Comparisons

- [Outbox vs Claude Artifacts](https://out-box.dev/en/guides/vs/claude-artifacts): Claude Artifacts publishes what Claude makes. Outbox stores and shares what any agent publishes, with password-protected links, expiration and version history.
- [Outbox vs ChatGPT Sites](https://out-box.dev/en/guides/vs/chatgpt-sites): ChatGPT Sites builds and hosts apps from ChatGPT. Outbox is the library where any agent publishes pages with their own URL, version history and protected links.
- [Outbox vs Stacktree](https://out-box.dev/en/guides/vs/stacktree): Stacktree and Outbox both publish your agents' HTML to private URLs. Outbox adds a library with folders, versions with diff, comments, daily documents and a public gallery.
- [Outbox vs DocSend](https://out-box.dev/en/guides/vs/docsend): DocSend tracks the PDFs and decks you upload. Outbox publishes the live HTML your agent builds, straight from the agent, with versions and protected links.
- [Outbox vs Qwilr](https://out-box.dev/en/guides/vs/qwilr): Qwilr builds interactive proposals in its own editor. Outbox publishes the HTML proposal your agent already wrote, with version history and protected links.
- [Outbox vs Derive](https://out-box.dev/en/guides/vs/derive): Derive is a self-hostable workspace for AI artifacts with deep review. Outbox sends agent work to specific people with per-person links, open alerts and flat pricing.
- [Outbox vs Display.dev](https://out-box.dev/en/guides/vs/display-dev): Display.dev gates agent output behind company SSO for internal teams. Outbox sends it to outside people with a link each, open alerts and expiry.