Deploy an application to sota.io. The platform auto-detects your framework and builds a Docker image automatically:
- Next.js: Detected via next.config.js/ts. Add output: 'standalone' to next.config for optimal builds.
- Node.js: Detected via package.json with a "start" script. Works with Express, Fastify, Koa, Hapi, etc.
- Python: Detected via requirements.txt or pyproject.toml. Works with Flask, FastAPI, Django.
- Custom Dockerfile: If a Dockerfile exists in the project root, it takes priority over auto-detection. Use this for Go, Rust, Java, or any other language. The EXPOSE directive in the Dockerfile is used to detect the app port automatically.
THREE WAYS to supply the source code — pick EXACTLY ONE:
1. **files** (inline source from AI):
Pass a map of relative paths to UTF-8 text content. Best when you've just
generated a small app in this conversation and want to deploy it without
any filesystem step. Up to 200 files, 10 MB total. Include
the framework manifest (package.json, requirements.txt, or Dockerfile)
so auto-detection works.
2. **git_url** (clone a public repo):
Pass an https://, git://, ssh://, or git@host:path URL. We shallow-clone
it (--depth=1 --single-branch) on the server and deploy. Optional
git_branch picks a non-default branch. Only public repos are supported in
v1. Max 200 MB after clone.
3. **directory** (local filesystem):
Pass an absolute path. Only works when the MCP client has filesystem
access (Claude Code / CLI; not Claude.ai web). Defaults to the current
working directory when omitted.
IMPORTANT: Your app MUST listen on the PORT environment variable. For auto-detected frameworks (Next.js, Node.js, Python) PORT is 8080. For custom Dockerfiles, the port is auto-detected from the EXPOSE directive (e.g. EXPOSE 3000 sets PORT=3000). If no EXPOSE is found, it defaults to 8080.
Every project includes a managed PostgreSQL 17 database. Six environment variables are auto-injected into your container — no manual database configuration needed: DATABASE_URL (full connection string), PGHOST, PGPORT, PGUSER, PGPASSWORD, and PGDATABASE. Libraries that follow libpq conventions (node-postgres, pgx, psycopg2, Django) pick up the PG* variables automatically with no configuration. If your app needs database migrations, run them on startup.
Deployments use blue-green strategy for zero downtime. The old container keeps running until the new one passes health checks (60s timeout). Use get-logs to monitor build progress. Files matching .gitignore, .git/, node_modules/, .env, and .DS_Store are excluded from the archive.