Getting started
vastframe is a private cloud for internal apps. People in your company describe an app to Claude or Copilot, and the app deploys onto vastframe with company sign-in, its own Postgres database, file storage and IT-approved integrations already in place. IT keeps an owner, a cost and a kill switch for every app.
Pick a starting point
What is vastframe?
The problem it solves and how it differs from a general-purpose cloud.
Key concepts
Organizations, projects, deployments, the Edge, the Hub, integrations, grants and access requests.
Quickstart
Deploy your first app from an AI assistant, the CLI or the console.
Architecture
How a request travels from the browser through the Edge to your app and its data.
Run it locally
The full platform on a laptop with Docker, no Azure account needed.
Walkthrough: a team app
A purchase-request tracker with a database, row-level security, roles and receipts.
Who these docs are for
| You are | Start with |
|---|---|
| Someone who wants to ship an app (an analyst, an ops lead, a developer) | Quickstart, then Building apps |
| An AI agent, or someone configuring one | Agents & MCP and the SDK reference |
| IT or a platform admin | Key concepts, Administration and Integrations |
| A security reviewer | Architecture, Multi-tenancy and isolation and Access & security |
vastframe is in early access. The whole platform described here is built and tested on the local stack (Docker, with local stand-ins for Azure, Entra and the vendors). Pieces that need real Azure services, such as Container Apps, Key Vault and Microsoft Graph on behalf of the user, are being connected now. Pages call this out with an Availability note wherever it matters.