Blog · July 1, 2026 · Rich Chetwynd
A public form out front, private results behind your login
Ask your assistant for a survey and it ships the whole thing — a public link anyone can open, with every response kept private to you.
A lot of small software is really two things stitched together: a page the public sees, and the private side where the results live. A survey and its answers. An RSVP and the guest list. A feedback form and the dashboard you actually read.
On Croft your assistant builds both in a single prompt. Ask for a survey and you get a public link anyone can open — no login, no account, nothing tracked — plus a private results page on your croft, behind your sign-on, for you and anyone you invite.
That split is the useful part. The public side is genuinely public, so you can share it anywhere. The private side is guarded by the same enterprise sign-on that protects everything else on your croft — so responses, submissions, and totals stay with your team, not scattered across a third-party form service you’ll be chasing for an export later.
It’s the shape of dozens of everyday jobs: a booking request where customers pick a time and you confirm on a private page; a waitlist where people join with an email and you see the list; an anonymous suggestion box for your team; an event RSVP with a running headcount. Idea to working form in minutes — public page and private results, in one go.
The one thing Croft still won’t do is a public product where strangers create their own accounts and log in. Publish a page, collect the responses — yes. Run a storefront for the internet — that’s app-builder territory, and we’ll point you there. The login side is for the people you invite. Deliberately.
Stake out your croft.
Your team's first app could be live before lunch.
Get your croft7 days free, no card to start. From $24/month — cancel anytime and take everything with you.