Runtimes and detection
"Deploy this folder" works without configuration because vastframe inspects the folder and picks a build. You can always override the result with tc.json or by adding a Dockerfile.
Detection order
Detection runs in the primary service's folder (the root, or path from tc.json):
- A
Dockerfileis built as-is. Anything goes. The port isportfromtc.json, else the firstEXPOSEin the Dockerfile, else 8080. - A
package.jsonmeans Node.js (see below). - A
requirements.txtorpyproject.tomlmeans Python (see below). - An
index.htmlwith no build system is a static site, published as-is (oroutfromtc.json).
If none match, the deploy fails with: Could not tell how to run this folder. Add a Dockerfile, a package.json (Node), a requirements.txt (Python), an index.html (static site), or a tc.json with "type", "build" and "start".
Node.js
| Folder looks like | Build kind | What runs |
|---|---|---|
next in dependencies | nextjs | npm run build (or npx next build), then npm start (or npx next start). A server, not static |
vite without a server framework | vite-static | npm run build, then the output folder (dist, or out) is served by the Edge as a static site |
| Express, Hono, Fastify, Koa or NestJS, or any other Node app | node | The build script if present, then npm start, else node + the first of main, server.js, index.js, app.js, main.js, server.mjs, index.mjs |
Node builds use node:24-alpine, install with npm ci when a package-lock.json exists (else npm install), and set NODE_ENV=production. A static Node project needs a build script (or build in tc.json).
Python
| Folder looks like | What runs |
|---|---|
start in tc.json | That command |
| Streamlit in requirements | streamlit run <file> --server.port $PORT --server.address 0.0.0.0 --server.headless true, for the first file that imports streamlit |
| FastAPI in requirements | uvicorn <module>:<app> --host 0.0.0.0 --port $PORT, for the file that has app = FastAPI(...) (uvicorn is added if missing) |
| Flask in requirements | gunicorn -b 0.0.0.0:$PORT <module>:<app>, for the file that has app = Flask(...) (gunicorn is added if missing) |
main.py, app.py or server.py | python <file>; it must listen on $PORT |
Files are searched in the order main.py, app.py, server.py, streamlit_app.py, api.py, then the rest alphabetically. Python builds use python:3.12-slim and install requirements.txt (or the pyproject.toml project).
Static sites
Static sites (plain HTML, or the output of a Vite build) are served directly by the Edge: no container, no cold start, near-zero cost. They have no server-side runtime, so environment variables don't reach them; use the browser SDK, which talks to /_tc/* on the same origin, or add an API service in another project.
Listening on $PORT
Container services must listen on 0.0.0.0:$PORT. PORT is 8080 unless you set port in tc.json or EXPOSE another port in your Dockerfile. The deploy waits for the app to answer before promoting it.
The SDK in builds
If package.json depends on @tenantcloud/sdk (any version, for example "*"), the build supplies the SDK that matches the running platform: it is copied into the build context and the dependency is rewritten to that copy. A lockfile entry that pins the SDK is dropped. Python projects that list tenantcloud in requirements.txt get the matching Python SDK. No private registry is involved; the SDK's own dependencies come from the public registries. Cron and worker services with their own package.json get it too. Folders built from your own Dockerfile are left as they are: install the SDK yourself in that case.
Supported today
| Runtime | Status |
|---|---|
| Dockerfile | Supported |
| Node.js: Express, Hono, Fastify, Koa, NestJS, Next.js | Supported |
| Vite (React, Vue, Svelte…) as a static site | Supported |
| Python: FastAPI, Flask, Streamlit, plain scripts | Supported |
| Plain HTML/CSS/JS | Supported |
| Other frameworks (Astro, Django, .NET…) | Use a Dockerfile |