From a folder, GitHub or an AI
sf init reads the repo and writes the config. Vite, Next.js, Astro, Python, Rust and more.
01 The AI-native small cloud
Build with Claude Code, Cursor, ChatGPT or Lovable. Run sf deploy. Your app is live behind your company sign-in, on its own network, with encrypted secrets and its own database. In your cloud or ours.
Self-serve sign-up is coming · enterprise installs in your own AWS account are available now.
$ sf deploy Packing helloworld… 412 KB (skipped node_modules, .env) ✓ built ✓ deployed ✓ healthy → https://helloworld-dev.smallfield.app 🔒 sign-in required · only Northwind can open it
02 How it works
Ask your assistant, or run one command. It acts as you, with your permissions. It cannot change who can open the app, and it never sees a secret value.
Prompt
Build a hello page for the Northwind team with a visitor counter, then put it online.
Done: one page, a counter saved in Postgres,
smallfield.json written. To ship it:
$ sf deploy
Claude Code, ChatGPT or claude.ai, connected once over MCP.
sf deploy
$ sf deploy building helloworld… pushing image… applying… ✓ healthy https://helloworld-dev.smallfield.app
Its own namespace, network policy, secrets and database.
Secured URL
Sign in to Northwind
Continue with Google Email me a codeSign-in required · your team only
Connect once: claude mcp add --transport http small-field https://console.smallfield.ai/mcp
03 Features
sf init reads the repo and writes the config. Vite, Next.js, Astro, Python, Rust and more.
One line in smallfield.json. A read-only explorer, backups and restore.
Run a report every Monday, or sf run report with input, with logs.
Every deploy is a release. Roll back or promote to production with no rebuild.
Uploads up to 10 GB and email sending, without a single key in front-end code.
Dev and preview apps sleep after 30 quiet minutes and wake on the next visit.
04 Secure by default
AI-built apps ship with the same mistakes. Small Field closes them before the first visitor arrives.
05 In your own cloud
Small Field installs into your own AWS account. Connect Entra or Okta once, and every app anyone deploys is behind it.
06 Pricing
Draft placeholders. No prices are public yet. Free and Team need the hosted service and self-serve sign-up, both coming.
A team of up to about 25
$X per developer / month + usage
One person trying it
$0 forever
A firm that wants it in its own cloud
Talk to us annual licence + your cloud bill
| Limit | Free | Team | Enterprise |
|---|---|---|---|
| Hosting | Small Field hosted | Small Field hosted | Your AWS account |
| Apps | 3, sleep after 30 min | Unlimited | Unlimited |
| Database | 1 small Postgres | Per app, daily backups | Your database pool |
| Support | Community | Named contact |
07 Questions
Usually none. Your server listens on process.env.PORT; that is it. To know who is signed in, read one header or call sf.identity.fromRequest(req).
Vite, React, Vue, Angular, Next.js, Nuxt, SvelteKit, Astro, Remix, plain HTML; Node and Bun servers; Python and Rust; or bring your own Dockerfile.
Yes. Connect the MCP server once; the assistant can create projects, deploy, read logs, run jobs, roll back and run read-only SQL, all as you. It cannot change who can open an app and never sees a secret value.
In an enterprise install, in your own AWS account: your cluster, your Postgres, your KMS keys, a registry with no internet address. A hosted service is coming.
Ask a platform admin. You can open a few paths (a health check, a webhook) yourself in smallfield.json; a whole public app is an admin decision, on purpose.
With SCIM, Entra disables them and they are signed out of every app, the console, the CLI and the API within minutes. Without SCIM, an admin clicks Disable.
No. sf init writes the config and the build needs no Dockerfile. Kubernetes runs underneath; you never touch it.