01 The AI-native small cloud

Build anywhere, deploy securely.

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.

~/helloworld
$ 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

From prompt to production, with the guardrails already on.

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.

  1. Prompt

    Ask for the app

    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.

  2. sf deploy

    Built without a Dockerfile

    $ sf deploy
    building helloworld…
    pushing image…
    applying…
    ✓ healthy
    https://helloworld-dev.smallfield.app

    Its own namespace, network policy, secrets and database.

  3. Secured URL

    Live, behind your sign-in

    🔒 helloworld-dev.smallfield.app

    Sign in to Northwind

    Continue with Google Email me a code

    Sign-in required · your team only

    Open Invite

Connect once: claude mcp add --transport http small-field https://console.smallfield.ai/mcp

03 Features

Everything an app needs, nothing you have to set up.

Deploy

From a folder, GitHub or an AI

sf init reads the repo and writes the config. Vite, Next.js, Astro, Python, Rust and more.

Data

Postgres per app

One line in smallfield.json. A read-only explorer, backups and restore.

Jobs

Cron and on-demand jobs

Run a report every Monday, or sf run report with input, with logs.

Releases

Rollback in one step

Every deploy is a release. Roll back or promote to production with no rebuild.

Files and email

No keys in the browser

Uploads up to 10 GB and email sending, without a single key in front-end code.

Cost

Sleeps when nobody looks

Dev and preview apps sleep after 30 quiet minutes and wake on the next visit.

04 Secure by default

Secure by default, because the person deploying should not have to know.

AI-built apps ship with the same mistakes. Small Field closes them before the first visitor arrives.

  • A door on every app. Company sign-in before any request reaches your code.
  • Your own island. One namespace and network policy per app; the cluster and cloud metadata are unreachable.
  • Secrets that stay secret. Encrypted with KMS, write-only, never in logs. .env never leaves your laptop.
  • Hardened containers. Non-root, read-only filesystem, no capabilities, memory caps.
The AI wrote this
Small Field does this
An /admin page with no login
Strangers land on the sign-in page; colleagues not on the list see "No access".
An API key pasted into the code
sf init moves it into an encrypted secret; server keys never reach the browser bundle.
The app fetches any URL a user types
The cloud metadata service and other apps are blocked: connection refused, not a token.

05 In your own cloud

Your cloud, your identity provider, your logs.

Small Field installs into your own AWS account. Connect Entra or Okta once, and every app anyone deploys is behind it.

  • Your accountOne cluster, one Postgres, your KMS keys. Code and data never leave it.
  • Your identity providerOIDC, SAML 2.0 and SCIM. Leavers lose every app within minutes.
  • Keeps runningWorks even if Small Field's own service is down. Logs stay in your account.

06 Pricing

Start alone, grow into a team, or run it in your cloud.

Draft placeholders. No prices are public yet. Free and Team need the hosted service and self-serve sign-up, both coming.

Free

coming

One person trying it

$0 forever

  • 3 apps, sleep after 30 minutes
  • Email code sign-in
  • 1 small Postgres
  • AI tools over MCP
  • 30-day access log

Enterprise

available

A firm that wants it in its own cloud

Talk to us annual licence + your cloud bill

  • Runs in your AWS account
  • OIDC, SAML, SCIM, groups, guests
  • Shared-key gateway with caps
  • Named contact and install help
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 Email Named contact

07 Questions

Questions people ask first.

Does my app need any code changes?

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).

What frameworks and languages work?

Vite, React, Vue, Angular, Next.js, Nuxt, SvelteKit, Astro, Remix, plain HTML; Node and Bun servers; Python and Rust; or bring your own Dockerfile.

Can ChatGPT or Claude really deploy for me?

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.

Where do my code and data live?

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.

How do I make an app public?

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.

What happens when someone leaves the company?

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.

Do I need to know Docker or Kubernetes?

No. sf init writes the config and the build needs no Dockerfile. Kubernetes runs underneath; you never touch it.

Start enterprise trial Talk to us