Questions people ask.

No. You need to know how to describe what you want, complain when it’s not right, and recognise when it’s right. That’s the job now.

An account with Claude, ChatGPT, or Grok (or any assistant that speaks MCP) - that’s what does the building. Claude and Grok work on their free plans; ChatGPT needs Plus or better, because its connector support isn’t on the free tier. Croft doesn’t resell AI or meter tokens - the AI is your own account.

On your own private server, hosted in a professional data centre, managed by us, owned in every meaningful sense by you. Not in a shared pool with everyone else’s apps.

Your apps are private by default - nobody without an invitation can even see a login page’s far side. Backups run continuously to separate storage, deploys are reversible, and the login system is ours (battle-tested), never AI-generated per app. We’d rather be boring than clever about this.

If you know them by name and there’s a handful of them - yes, invite them like anyone else (a client portal for your five biggest customers is a classic croft). You can also put a public page in front of an app - a booking request, a feedback form, a survey - that anyone can use, with the results kept private to you. A full storefront where strangers create their own accounts is still app-builder territory, and we’ll cheerfully point you there.

Yes. An app can have a public page - a survey, a feedback form, an RSVP, a booking request - that anyone can open with a link, no login and no account. The submissions and results stay on the private side of your croft, behind your sign-on. Your assistant can build and deploy the whole thing, public page and private results, in a single prompt. What Croft still doesn’t do is public products where strangers create their own accounts and log in.

Native mobile apps (croft apps work great in a phone browser, though), anything meant to serve thousands of people, and public products where strangers create their own accounts and log in. You can publish public pages and forms - a survey, an RSVP - but the login side is for the people you invite. Deliberately.

Tell Claude. It can read your croft’s logs, fix the app it built, and redeploy it. If something breaks on our side - the server, backups, the login - that’s our job, and we’re on it before you notice.

Not right now, and it’s not on the plan. Every croft gets its own address on oncroft.net, and your apps live at tidy subdomains like bookings.yourcroft.oncroft.net - with HTTPS handled for you, nothing to set up. One less thing to own.

They’re yours to take, either way. Cancel and we hand you a single export of every app’s code, database, and files, packaged as a standard Docker setup that any developer can run - and if Croft ever went away, you’d still have exactly that. No lock-in, no proprietary format. Full detail: Your data & export.