A croft is a small plot you tend yourself. Ours come with help.

A small private server. The handful of apps your work or family actually needs. And Claude to do the building and the fixing, so owning it never becomes a second job.

The conversation is the workshop.

You don’t build in Croft. You build in Claude — the same place you already think things through. Connect your croft once, and from then on “make me an app that…” ends with a working link. Change your mind next month? Open a chat: “add a column for deposits and let Sam approve them.” Claude fetches the code from your croft, changes it, redeploys. The app grows the way your needs grow: conversationally.

Your login, in front of everything.

Every croft comes with its own front door: a login page for your workspace. Every app you build automatically lives behind it. When Claude builds an app, the app itself never handles passwords or sign-ins — the door does. This is why a Croft app can’t leak your data through a botched login screen: there’s nothing to botch. Your people sign in once, with a passkey (Face ID, fingerprint, or their phone), and every app just knows who they are.

People, not user accounts.

The People page is a list of humans you trust: name, email, and which apps they can open. Add someone, they get an email, they’re in. Remove someone, they’re out of everything, instantly. That’s the entire admin experience. We designed it for the day an employee quits and the day your daughter turns eight and earns chore-chart access — the two extremes of real-world user management.

A server with your name on it.

Under every croft is a real virtual private server — a small, capable machine that costs a few dollars a month to run, which is why we can charge a flat price. It has its own address on the internet. Your apps run there. Your data lives there. We look after it: security patches, backups, monitoring, updates, all invisible. And if you ever outgrow us or just want to go it alone, the server, the code, and the data are yours to take. We’ll even hand you the keys — SSH and all.

When it breaks.

Software breaks. Ours does too. The difference is what happens next: you tell Claude “the booking page is showing an error”, and Claude reads your croft’s logs, finds the bug it wrote, fixes it, and redeploys — usually before you’ve made tea. Every deploy is reversible with one click, and every database is continuously backed up off the server. We schedule actual restore drills, because a backup nobody’s tested is just a hope.

Stake out your croft.