From artifact to app

What you'd build

The artifacts worth keeping.

A financial model your team can actually fill in

A pricing calculator that saves every quote

A dashboard that remembers its data

A form whose responses you can read later

An internal tool the whole team can open

A tracker that's still there tomorrow

A mockup, turned into the real thing

A checklist your crew ticks off together

A survey with a public link, results kept private

What’s an artifact?

When you ask an AI assistant to make you something visual — a page, a chart, a little tool — it often builds it as an artifact: a self-contained bit of HTML and code that renders right there in the conversation, next to the chat, so you can see it and refine it on the spot. Claude calls them Artifacts; ChatGPT has Canvas; the others have their own version.

They’re one of the best things about building with AI: instant, visual, and easy to change by just asking. You describe a financial model, and a working one appears — fields to fill in, numbers that update as you type.

Why an artifact isn’t an app (yet)

An artifact is a preview. It lives in your chat window and runs only for you, in that moment. That’s perfect for a sketch — but the second it’s genuinely useful, you hit a wall:

You can’t really share it. A screenshot or a file isn’t the same as a link someone can open and use.
It doesn’t remember anything. Type numbers into that financial model, close the tab, and they’re gone. There’s no database behind it.
It’s not yours to keep. It’s tied to the chat. Next week, when you want it again, you’re recreating it from scratch.

The financial model is the perfect example: brilliant on your own screen, and useless the moment you need your team to use it or the results to stick.

How Croft turns an artifact into an app

You don’t start over. Ask your assistant — connected to your croft — to deploy the artifact, and it becomes a real app: hosted at its own web address, with a real database so data is saved, behind one login for the people you invite. The same conversation that made the artifact makes it real.

That’s the whole idea of Croft. Your AI is great at making the thing; Croft is where the thing lives, gets shared, and keeps working.

The platform

What you get when an artifact becomes a Croft app.

Everything an artifact is missing — a home, a memory, a way to share it safely — Croft adds the moment you deploy.

A live web address

Not a screenshot or a file to email — a real URL your people open in a browser, on any device. The artifact becomes something you can actually hand to someone.

Data that sticks

A real database behind the app, so what people type in is saved and still there next time. That financial model finally remembers its numbers.

Shared, privately

Invite people by name; they sign in once through enterprise single sign-on. It's for the people you choose — not a public link for strangers.

Still there next week

It's a real app on your own private server, backed up and reversible — not a preview that vanishes when you close the chat.

It can grow

Ask for changes any time, connect it to your other tools, or put it on a schedule. Artifacts can't do any of that; Croft apps can.

Yours to keep

Export the whole thing — code, database, files — and run it anywhere Docker does. No lock-in, ever.

FAQ

Frequently asked questions

What is an AI artifact?

An artifact is a self-contained piece of HTML and code that an AI assistant generates and renders inside the conversation — a page, a calculator, a dashboard, a form — so you can preview and refine it on the spot. Claude calls them Artifacts; ChatGPT has Canvas; other assistants have their own version.

What's the difference between an artifact and an app?

An artifact is a preview that runs only for you, in the chat, with no database and no link others can open. An app runs on a server at its own URL, saves data, and can be shared with the people you invite. Croft turns an artifact into an app.

Can I turn a Claude or ChatGPT artifact into a real app?

Yes. Ask your assistant, connected to your croft, to deploy the artifact. It becomes a real app on your own private server — a live URL, a real database, and one login — without starting over.

Why can't I just share the artifact itself?

An artifact lives in your chat window and runs only for you; there’s no link others can open and use, and nothing is saved between sessions. Deploying it to Croft gives it a web address, a database, and sign-on.

Do I need to know how to code to deploy an artifact?

No. You ask your assistant in plain words to deploy it to Croft, and it handles the hosting, database, and login for you.

From artifact to app.