What is vastframe?
vastframe is the landing zone for AI-built internal apps. It gives the dashboards, trackers and small tools that people now build with AI assistants a safe, governed place to run inside the company.
The problem
AI assistants have made it easy for anyone to build a working internal app in an afternoon. A finance associate can ask for a budget-vs-actuals dashboard, or a support lead for an escalations board. The hard part is everything after the code exists:
- Where does it run? Personal cloud accounts and laptops are invisible to IT.
- Who can open it? Writing sign-in code is error-prone, and AI-generated auth code is a liability.
- Where does the data live? Apps need a database and files, ideally without anyone handling connection strings.
- How does it reach business systems? Salesforce, SharePoint, Teams and the ERP need credentials that should never sit in app code.
- Who owns it next year? Apps outlive their authors' interest, and sometimes their employment.
What vastframe does
| For the person building the app | For IT |
|---|---|
Deploy a folder from Claude, Copilot, the tc CLI or by dragging it into the console | Every app has an owner, a place in the org chart and an expiry |
| Company sign-in in front of every app, with no auth code | Access follows the directory: teams, departments, groups and app roles |
| A Postgres database per project with a Supabase-style Studio and row-level security | Cost per app, rolled up by reporting line, department or group, with a chargeback CSV |
| File storage with buckets, quotas and signed links | An integration catalog with approvers, maximum scopes and auto-approve policies |
| Microsoft 365, Teams, Salesforce and on-prem SQL through one SDK | Every integration call audited; a kill switch per app and per user |
| Missing permissions are requested automatically; the app goes live anyway | Approvals in Teams or the console, with the code lines that need the access |
Design principles
- Zero secrets in app code. Identity, database access and integrations are brokered by the platform. An AI-generated app can't leak a key it never had.
- The directory is the source of truth for people. Who someone is, who they report to and which groups they belong to comes from your identity provider (Microsoft Entra ID, another OIDC provider, a SCIM directory, or people you manage in vastframe).
- Reuse what agents already know. The database speaks Supabase/PostgREST query syntax, SQL is standard Postgres, and integrations pass through to the vendors' own REST APIs.
- One API, many faces. The console, the MCP server, the CLI and the SDK all sit on the same Hub API, so anything you can click you can also script or ask an agent to do.
- Deploys never dead-end on permissions. If an app needs access it doesn't have yet, vastframe files the request with the details an approver needs, deploys the app, and the feature starts working the moment someone approves.
What vastframe is not
- Not git hosting. Every deployment keeps its exact source bundle, so rollback and "continue editing elsewhere" work without git. Bring your own git if you want it.
- Not a low-code builder. Apps are ordinary code (React, Node, Python, a Dockerfile, plain HTML). vastframe runs and governs them; your assistant writes them.
- Not a replacement for your identity provider. It signs people in through the provider you already use.
Where to go next
- Key concepts explains the vocabulary used throughout these docs.
- Quickstart gets an app live in a few minutes.
- Deployment options compares vastframe cloud with running it in your own Azure subscription.
Was this page helpful?