Do I need to know how to code?
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.
Do I need a GitHub account or a terminal to deploy?
No. Developer platforms like Railway, Supabase and Vercel expect you to push code to GitHub and wire up hosting yourself. On Croft you ask Claude or ChatGPT to put the app live, and Croft handles the rest: it keeps the code and every version of it, deploys updates with zero downtime, adds your company login, and monitors the app so you hear about problems straight away. Developers can still work in Cursor or Claude Code against the same croft.
Which AI assistant account do I need?
Ideally the one you already have: Claude, ChatGPT, or Grok (or any assistant that speaks MCP). Claude and Grok work on their free plans; ChatGPT needs Plus or better, because its connector support isn’t on the free tier. Using your own AI costs nothing extra on Croft. No AI subscription? Ask Croft, the AI built into your croft, can build for you instead, paid for with optional credits.
What can my apps connect to?
Any tool, database or API your business uses. Connectors work with any REST API that takes a key or OAuth, plus SMTP email and AWS, so your accounting system, CRM, payments, a database behind an API, or your own internal API are all fair game. Croft holds the keys; your apps and your AI never see them. A few tools, such as Xero, Stripe and Google Search Console, also have ready-made syncs that keep a copy of their data for your AI to query.
Where do my apps actually live?
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.
How big is my server?
Every workspace gets its own server with 2 vCPU, 4 GB of RAM and 40 GB of disk, not a slice of a shared one. There’s no limit on apps: it comfortably runs dozens of typical team tools, with continuous backups kept off the server. If your apps outgrow it, move up a plan and Croft resizes your server for you.
Is my data safe?
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.
Can my customers use my apps?
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.
Can I make part of an app public?
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.
What kinds of apps can't Croft do?
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.
What happens when something breaks?
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.
Can I use my own domain?
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.
What happens to my apps if I leave, or if Croft disappears?
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.
How do I deploy this app so only my team can use it?
Deploy it to Croft: the app goes live behind company login with passkeys, and you invite your team by email. Each person you add can access only the apps you grant them. See Deploy with your AI agent or How to share an app you built with AI - privately.
Where can I host an internal app I built with Claude/Cursor behind company login?
Croft is built for this: your AI deploys via MCP, the app lives on your private server, and company login sits in front of every app. The trade-off is that Croft doesn’t fit consumer-scale public products. See Host a Cursor app or Deploy a Cursor app for your company.
Best way to share a vibe-coded app privately with my team
Deploy to Croft so it has a real URL behind company login, then invite your team. Each person signs in once with a passkey and can use any app you’ve granted them access to. See Where to host a vibe-coded app privately.
Railway vs alternatives for private internal apps
Railway is a developer PaaS for deploying services and databases to the internet. Croft is built for private team apps: private by default, company login and per-app access included, and flat pricing with no usage meters. If your app needs Postgres or multiple services, Railway fits; if it’s an internal tool fine on SQLite, Croft is simpler. See Croft vs Railway for private team apps or Compare Croft and Railway.
How do I deploy a full-stack app with a database privately?
Deploy to Croft: every app gets a SQLite database at /data/app.db, company login, backups, and rollback. The trade-off is that if your app needs Postgres, queues, or multiple services, Croft isn’t the fit — it’s optimized for internal apps on SQLite. See Private full-stack deploy with database.
Supabase alternative for internal team apps
Croft is not a Postgres backend-as-a-service like Supabase — it’s an app platform for internal tools behind company login, with a SQLite database per app. If your app needs Postgres, realtime, or edge functions, Supabase fits better; if it’s an internal tool fine on SQLite, Croft is simpler and includes the login. See Supabase alternatives or Compare Vercel and Supabase.
Your team’s first app could be live tonight.
Free for a day, and a week once your first app is live. No card needed.
Free to try. No card needed.