Guides
Plain answers for people who built an app with an AI assistant and now need colleagues to use it.
- Before your team uses it: a security checklist for an app you built with AITen checks you can run on any host, with what Haechy does by default.
- How to add a custom connector to ClaudeSteps by plan, what a Team or Enterprise Owner does, and fixes for the errors people meet.
- Where to host an app you built with ClaudeWhat kind of host your app needs, what you would set up yourself, and what it costs a month for ten people.
- How to share a Claude artifact, and who can open itWho can open an artifact on each plan, for each way of sharing, and when people need a Claude account.
- What is the safest way to share an app you built with Claude?When a shared Claude artifact is enough, and when the app needs its own sign-in and database.
- Giving colleagues access without making them create accountsA one-time emailed link, the work email people already have, or an open link, and what each risks.
- MCP connectors that can deploy a web appWhich hosts and clouds let your assistant put an app online, and what each is for.
- Hosting a small internal tool that needs a database and loginsFour routes, with a worked cost for a ten-person app.
- Hosting an internal app with its data in the EUWhat can stay in the region and what may not.
- Keep your API keys out of the code Claude writesWhere keys go instead, what secret scanning catches and misses, and the first ten minutes if one leaks.
Setup steps and reference pages are in the documentation. Side-by-side pages on other hosts are on the compare page, and pricing is on the pricing page.