Deployment options
vastframe runs the same code in two shapes.
| vastframe cloud (SaaS) | Self-hosted in your Azure | |
|---|---|---|
| Who operates it | vastframe | Your IT, inside your Azure subscription |
| Organizations per installation | Many, isolated by Postgres row-level security | One (the default tenant) |
| Your address | <org>.vastframe.app (console.<org>…, <app>.<org>…) | Your domain, for example apps.contoso.com |
| Sign-in | Email links, Microsoft Entra ID, any OIDC provider, or SAML SSO through WorkOS | Your Microsoft Entra ID tenant |
| Directory | People and groups managed in vastframe, or synced from your identity provider | Synced from Microsoft Graph |
| Where data lives | vastframe's cloud | Your subscription: code, data, credentials and identities stay in your tenant |
| Billing | Licence from vastframe | Azure Marketplace (planned), counting toward your Azure commitment |
| Status | Early access | Coming soon |
vastframe cloud
Try vastframe as SaaS with no Azure footprint.
Self-hosted in Azure
A Managed Application in your subscription.
Multi-tenancy and isolation
How organizations are kept apart, for security reviewers.
Domains and network
Subdomains, certificates, fallbacks and network exposure.
Data residency
Where code, data, credentials and logs live.
Platform status
What runs today, and what's coming to Azure.
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?