How to share an app you built with AI — privately

Short answer: To share an AI-built app privately, deploy it to a host that gives it a real web address behind a login — like Croft — then invite people by name. They open a link, sign in once, and use it. No public URL, no accounts for strangers.

The trouble with an app your AI built in the chat is that there’s nothing to send. A screenshot isn’t the app. A file only works if the other person can run it. And a raw public link would let anyone in. Sharing something real, but keeping it private, needs a proper home.

How to do it

1. Deploy the app to your croft. Connect an assistant and ask it to deploy the app. How to connect →
2. Invite your people. Add them by email on the People page and choose which apps each can open. They sign in with a passkey through your croft’s enterprise single sign-on.
3. Send the link. It’s a real URL they open in a browser, on any device — but only the people you invited can get past the login.

Private by default

Croft apps aren’t public. Access is yours to set, app by app, and everything sits behind one sign-on. Someone leaves the team? Remove them once and they’re out of everything, instantly.

Want part of it public — say a survey anyone can fill in, with the results kept private to you? That works too: a public page out front, private results behind your login. But the app itself, and its data, stay with the people you choose.

This is one of the three things that turn an artifact into a real app: a shareable link, a database, and a login.

More from the blog