Three ways to deploy
The console, the CLI and the MCP server all call the same Hub API.
From Claude or Copilot
Add the MCP server, then ask your assistant to deploy the folder.
“Deploy this folder to vastframe”From the terminal
The tc CLI uploads a folder and prints the URL.
tc deploy ./my-appFrom the browser
Drop a folder on New project in the console.
Projects › New projectBrowse the docs
Start with the quickstart, or jump to a reference.
Getting started
What vastframe is, the key concepts, and your first deploy.
Building apps
Deploys, tc.json, runtimes, previews, rollback, env vars, cron jobs and logs.
Data
A Postgres database per project, the Studio, row-level security and storage.
SDK reference
tc.db, tc.storage, tc.int, tc.m365 and tc.teams in JavaScript and Python.
Access & security
Who can open an app, the signed user identity, roles, approvals and audit.
Integrations
Microsoft 365, Teams, Salesforce and on-prem SQL, governed by grants.
Sign-in & identity
Entra ID, email links, any OIDC provider, SAML SSO and SCIM.
Administration
Org tree, cost, policies, people, roles, lifecycle and licences.
Deployment options
vastframe cloud or your own Azure, isolation and data residency.
Agents & MCP
Connect Claude, Copilot or any MCP client and deploy by asking.
CLI reference
Every tc command and flag.
API reference
The REST API behind the console, grouped by area.