The step beyond a Claude artifact

When an artifact is enough

If a few colleagues all have Claude accounts and the tool only has to remember a little text, an artifact does the job and costs you nothing to share. It can keep data between visits, private to each person or shared by everyone, up to 20 MB per artifact. Claude can run inside it, on the viewer's own plan. A checklist, a tracker, a one-off calculator: use an artifact.

Where an artifact stops

Anthropic's documentation describes an artifact like this: "An artifact is a capture of work: one self-contained page with no backend, so it can't serve multiple routes. For a hosted internal tool with a backend, deploy it on your own infrastructure instead." That is Anthropic's general advice, not a recommendation of Haechy. Haechy is a hosted place with a backend that you set up by asking Claude, so the tool stays something a person with no technical background can own.

In practice the edges show up in a few places. An artifact stores text only. It can't authenticate viewers itself. Its page can reach only its own origin and Google Fonts, and the connected apps it uses belong to each viewer, so every viewer connects their own account. We found no scheduled or background runs described on Anthropic's pages, only pages that refresh while someone has them open.

What it looks like in an office

A report that arrives on Monday morning. Say your finance team wants last week's invoices summed up before the stand-up. Every Monday at 8, the app pulls last week's invoices from your accounting tool and emails a summary to the finance team. A scheduled job runs on the server, so nobody has to open a page. Jobs run hourly on Free, every 5 minutes on Pro and every minute on Team and Business. On paid plans the summary can come from your own address, such as reports@yourcompany.com. App email goes only to people who have access to the app.

Expense claims with receipts. Say your team files claims with a photo of the receipt. The photo goes into the app's own file storage, kept in the app's region: 1 GB on Free, 10 GB on Pro, 50 GB on Team and 250 GB on Business. The claims themselves sit in the app's Postgres database, so finance sees every colleague's claims in one list next week and next month. An artifact's storage takes text only. Expense claims is one of Haechy's starter apps: ask Claude for it and it is running in one request, with receipt uploads, approval and a CSV export, ready for Claude to adjust.

A holiday tracker with a history. Managers approve requests, and the calendar updates for everyone at once, including people who already have it open. Then a Tuesday goes wrong and someone deletes the wrong rows. You ask Claude to restore last night's backup. Haechy saves a copy of today's data first, so the restore itself can be undone. Free keeps 7 days of nightly backups and paid plans keep 30. If it was a change to the app itself that went wrong, Claude puts the previous version of the code back in one step and leaves the data alone.

A stock check against your own system. Say the warehouse app needs the live count from your inventory tool. You approve that one service, once. Claude can ask for access to a new service but can't approve its own request: the owner, or an admin on Team and Business, says yes in the Haechy console. The app can then reach that service and nothing else. An app that can only reach the services you approved has fewer ways in or out than one put online with every door open. The app's Connections page shows that service, who approved it and why, and anything the app tried to reach that was blocked. When IT asks, Claude can make a read-only security summary to send them: who can sign in, the region, the approved connections, the last security check and the backups.

An equipment booking page on your own address. Start from Haechy's booking app, which already stops two people booking the same room or laptop. On a paid plan it can live at an address of your own, such as bookings.yourcompany.com: 3 addresses on Pro, 20 on Team and 100 on Business. Colleagues sign in with a one-time link sent to their work email. On paid plans people can also sign in with their Google or Microsoft work account. On every plan a colleague can add a passkey, so the next visit is one tap.

A form for people outside the company. On a paid plan an app can be public, so customers fill it in without signing in and their answers land in one table your team can sort. Public is a setting for the whole app, so keep the team-only tools in separate apps. Haechy shows you the pages anyone could open without signing in before it goes public, and you confirm it.

Who can open it

An artifact is opened by people in your Claude organization, invited people who have a Claude account, or anyone with a link where your plan allows it. People outside your organization who sign in can read an artifact's stored data but can't change it.

A Haechy app is private by default. You add people by email and they get a link that works once and expires in 15 minutes. They need no Haechy account, no password and no Claude subscription. On Pro, Team and Business you can open an app to everyone at your company's email domain, up to 20 domains per app. Everyone signed in uses the same app and the same database.

Where the data lives

Choose where the app lives: the United States, the European Union, the United Kingdom or Australia. The app, its database and its backups stay in that region. Two plain reasons to choose with care. People get a faster app when it sits close to them, and the app's stored data stays under your region's privacy rules with no international transfer of it to arrange (why the region matters). Anthropic's pages describe no region choice for claude.ai artifacts (read November 7, 2026).

Your Haechy account, sign-in records and app settings run on Haechy's control plane in the US. Some services we use to send email, verify phone numbers and take payments process data outside your chosen region. See our sub-processors. The regions page lists what lives where.

What it costs

The Free plan costs $0 and includes 2 apps and 5 people who can sign in. Pro, Team and Business are listed on the pricing page. Haechy has no per-request or function-call limits, because an app is a server that runs. The limits that do exist are CPU and memory, database storage, app emails a month and outbound data a month. Free apps sleep after 15 idle minutes and wake in a few seconds.

Questions

Can I keep using Claude to build?

Yes. You connect Haechy to Claude once, then ask Claude to put the app online. The steps are in the Claude setup guide. Claude, ChatGPT, Copilot and Cursor can all do it.

Does an artifact really keep data between visits?

Yes, up to 20 MB of text per artifact, either private to each person or shared. It suits small lists. Haechy is for records that keep growing and need backups.

Can colleagues sign in with a passkey or their Google account?

Passkeys work on every plan. Sign in with Google or Microsoft is available on paid plans.

Do my colleagues need Claude?

No. They open the link you send them.

Start with a small one

Put one real tool on the Free plan and invite two colleagues. Ask Claude to put the app online once Haechy is connected, and the setup guide shows the steps.

Haechy is an independent product of DT Global Ventures Ltd. It is not made, sponsored or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.