vastframe cloud
vastframe cloud is the SaaS edition: one shared installation serves many organizations (tenants). It exists so you can try vastframe without installing anything in Azure; each organization is isolated from the others by the database itself.
vastframe cloud is in early access. Multi-tenancy, licences, built-in accounts and bring-your-own sign-in are built and tested on the local stack. Hosted tenants are being onboarded with design partners; ask your vastframe contact for access.
Your organization
When your organization is created you get:
| Thing | Example |
|---|---|
| Domain | acme.vastframe.app |
| Console | https://console.acme.vastframe.app |
| Sign-in | https://auth.acme.vastframe.app |
| Apps | https://<app>.acme.vastframe.app |
| First Org Admin | The person named at sign-up |
| Integration catalog | Seeded with the standard integrations, ready for IT to configure |
Signing in
New organizations start with email links (vastframe accounts): people enter their email and get a one-time link, valid for 15 minutes, if they're a member of the organization. An Org Admin can switch the organization to Microsoft Entra ID, any OpenID Connect provider, or SAML SSO with SCIM directory sync through WorkOS in Admin › Sign-in. See Sign-in & identity.
People and groups
Until a directory is connected, Org Admins manage people and groups in Admin › People and Admin › Groups: invite, import from CSV with managers, turn people off, and nest groups. Access rules such as My team and My department, delegated admin scopes and the org chart all work the same as with Entra ID. See Administration.
Licence
Your organization's licence sets your plan, seats, project cap and features. Admin › License shows it. Seats count people who opened an app in the last 30 days; going over only warns. The project cap is a hard limit on new projects. After expiry and a grace period, new projects and deploys pause, but running apps keep serving. With no licence installed, nothing is gated.
The CLI and MCP in an organization
Organization hosts (such as console.acme.vastframe.app) identify the organization automatically. When the CLI talks to an address that isn't one of them, set the tenant slug explicitly:
TC_TENANT=acme tc deploy ./app
Under the hood this sends the X-TC-Tenant header. A request to the shared installation that names no tenant is refused.
Isolation
See Multi-tenancy and isolation for how each organization's data is kept apart.