How it works
Build an app. Everything it needs is already there.
No card. 7 days. Cancel anytime.
Describe an app to your AI assistant, or hand it a spreadsheet. It lands on your own private Croft server, behind your team's login, with a database, sign-on, schedules and monitoring built in.
Works with Cursor, Claude Code, ChatGPT & any MCP client•7-day free trial
Building blocks
What every app gets.
Apps
Every app runs in its own container on your server, and a deploy is just a commit.
- Node 22 + Hono, or Python + Flask
- Zero-downtime deploys
- One-click rollback
Auth
Single sign-on with passkeys in front of every app. No auth code in yours.
Schedules
Croft calls your app on a cron, through deploys and reboots.
File storage
Uploads handled by Croft, served from an isolated files host.
Connectors
Call any outside API without a key in your code.
Database
Every app has its own SQLite database, and apps can share data when you allow it.
- Persists across deploys
- Continuous off-server backups
- Sharing is off by default
Monitoring
Errors, metrics and logs, captured automatically. No SDK.
Secrets
Environment variables set in the app's settings, never in code or chat.
Ask Croft
Ask Croft to build, change, or query your apps.
Your server
A private server that's yours alone, and everything comes with you if you leave.
Use what you need. Everything's already wired together.
Technical specs
- Runtime
- One container per app, listening on
$PORT. Node 22 + Hono + server-rendered HTML by default; Python + Flask works too. - Deploys
- A deploy is a commit: Nixpacks build, then a zero-downtime swap behind the proxy. A failed build returns its log. Every deploy has a plain-language changelog message, and rollback restores the previous release.
- Database
- SQLite at
/data/app.db, in WAL mode. Numbered.sqlmigrations run at boot. Data persists across deploys, with continuous off-server backups. - Shared data
- Off by default. Share an app’s database and other apps can read and write it over an internal endpoint with a bearer token. Public apps can’t reach private data unless an admin approves.
- Sign-in
- Single sign-on with passkeys at Croft’s proxy. Your app gets the user’s email and workspace role (owner, admin, creator or member) as headers it can’t forge. Access is granted per app on the People page.
- Public paths
- Publish specific paths, like a webhook or a public form. Everything else stays behind sign-in.
- File uploads
- A platform upload endpoint with a 25 MB limit and file type checks. Files are served from an isolated files host, and your app never holds storage keys.
- Connectors
- Any HTTP API through Croft’s broker, including AWS with SigV4 signing. OAuth services connect with a button. Sensitive connectors can need an admin’s approval per app.
- Email & Slack
- SMTP connectors for sending email, and a Slack connector for posting and replying in Slack.
- Schedules
- 5-field cron, in UTC. Croft calls your endpoint with a signed header. Schedules survive deploys and reboots.
- Monitoring
- Grouped errors with stack traces; error rate, p50/p95, slowest routes, CPU and memory; time spent in the database and external calls; 7 days of searchable logs; email alerts. No SDK.
- Secrets
- Environment variables set by an owner or admin in the app’s settings. Encrypted at rest, never in code or chat.
- Server
- A dedicated virtual private server per workspace, patched, backed up and monitored by Croft. HTTPS on every app.
- Export
- Every app’s code, database and uploaded files as one package you can run yourself with Docker.
Bring your own agent
Croft is an MCP server. Build from the tools you already use.
Your own AI assistant can create apps, deploy, read logs and errors, roll back, set schedules, and manage connectors and access. It uses your own AI subscription, not Croft credits.
https://mcp.oncroft.net
Find your croft's exact link in your dashboard under Connect an AI assistant and copy it from there.
create_app
write_app_files
deploy_app
get_app_status
get_app_logs
get_app_errors
get_app_metrics
rollback_app
set_app_schedules
set_public_paths
set_database_sharing
query_app_data
grant_connector
Start here
What do you want to do?
- Connect Claude Code or Claude
- Connect Cursor
- Connect ChatGPT, Grok or Copilot
- Install the agent plugin
- Turn a spreadsheet into an app
- Host an app I built in Cursor
- Host a vibe-coded app privately
- Host a Claude-generated app
- Host a Grok-generated app
- What is an AI artifact
- Publish a public form
- Run something on a schedule
- Connect Stripe or another API
- Share data between apps
- Give my team access
- Read errors and logs
- Roll back a deploy
- Export everything
- Read the security model
For teams
One croft for the whole team.
Developers and non-developers build side by side, and every app gets the same guardrails.
- People, not user accounts. Add someone and they get an email. Remove them once and they're out of everything.
- Approval for sensitive data. An app can ask for a sensitive connector, but nothing happens until an admin says yes.
- Roles that match the work. Members use what's shared and can ask Croft about it, but can't change it.
FAQ
Frequently asked questions
How do I build an app on Croft?
Describe the app to Ask Croft in your workspace, or to your own AI assistant (Claude, ChatGPT, Cursor, Claude Code) connected over MCP. Or hand over a spreadsheet and say “make this an app.” It writes the code and deploys it to your private server, live behind your login, usually in minutes.
Can I turn a spreadsheet into an app?
Yes. Upload a spreadsheet to your assistant and ask it to turn it into an app. It builds a real app with a database and a tidy interface on your croft, ready to share with your team. No more emailing files around.
What stack do Croft apps use?
Each app runs in its own container and listens on $PORT. The default is Node 22 with Hono and server-rendered HTML; Python with Flask works too. Data lives in a SQLite database at /data/app.db, with numbered SQL migrations that run at boot. A deploy is a commit: Croft builds it with Nixpacks and swaps it in with zero downtime.
Can I use Cursor or Claude Code with Croft?
Yes. Croft is an MCP server, so Cursor, Claude Code, and any other MCP client can create apps, write files, deploy, read logs and errors, roll back, and set schedules. Connect it once from the connect guides, or install the official agent plugin. Your own AI assistant uses your own subscription, not Croft credits.
How is Croft different from Supabase?
Supabase is a backend you build against, and you host your frontend somewhere else. Croft hosts the whole app privately, behind your team’s login, with the database, auth, schedules, connectors, and monitoring built in. If you’re building a large public product, Supabase is a great fit. If you want private apps for your team without assembling a stack, that’s what Croft is for.
What happens when an app breaks?
You get an email alert. Your own AI assistant can read the errors, logs, and stack traces over MCP, fix the code, and redeploy. Or click Fix with Croft on the error and Croft handles it. Every deploy can be rolled back in one click.
How do I give my team access?
Add people once on the People page and choose which apps each can open. They sign in with a passkey. Remove someone once and they’re out of everything, instantly.
Do I need to manage a server or database?
No. Croft provides the private server, database, HTTPS, sign-on, and backups, and keeps the server patched and monitored. There’s nothing for you to configure or maintain.
Start your free trial.
Your team's first app could be live before lunch.
No card. 7 days. Cancel anytime.