Skip to main content

Deployment options

vastframe runs the same code in two shapes.

vastframe cloud (SaaS)Self-hosted in your Azure
Who operates itvastframeYour IT, inside your Azure subscription
Organizations per installationMany, isolated by Postgres row-level securityOne (the default tenant)
Your address<org>.vastframe.app (console.<org>…, <app>.<org>…)Your domain, for example apps.contoso.com
Sign-inEmail links, Microsoft Entra ID, any OIDC provider, or SAML SSO through WorkOSYour Microsoft Entra ID tenant
DirectoryPeople and groups managed in vastframe, or synced from your identity providerSynced from Microsoft Graph
Where data livesvastframe's cloudYour subscription: code, data, credentials and identities stay in your tenant
BillingLicence from vastframeAzure Marketplace (planned), counting toward your Azure commitment
StatusEarly accessComing soon

Which should I choose?​

  • Start on vastframe cloud if you want to evaluate quickly, don't have an Azure landing zone ready, or don't use Microsoft Entra ID.
  • Plan for self-hosted if your policy says business data and credentials must stay in your own Azure tenant, or you want spend to count toward your Microsoft commitment.

Both run the same code, so apps, tc.json, the SDK and the console work the same way. Moving between them is planned but not yet automated.

Was this page helpful?