Skip to main content

Self-hosted in your Azure

The self-hosted edition installs vastframe into your own Azure subscription. Code, data, credentials and identities stay in your tenant; vastframe's own services never hold your data.

Availability

Coming soon. The Azure Managed Application, its setup wizard and the Azure drivers (Container Apps, ACR Tasks, Key Vault, Azure DNS, Cost Management, Postgres Flexible Server with Entra authentication) are in development. The platform code is the same as on the local stack, where everything on this page is exercised with local stand-ins. This page describes the planned installation so you can review it.

What gets installed​

A Managed Application deploys into a managed resource group in your subscription:

ResourcePurpose
Virtual networkNetwork for the platform and app environments
Container Apps environment "system"The Hub (API, worker, sign-in), the Edge, the Integration Gateway, the storage service, the Studio backend
Container Apps environment "workloads"Your apps, their Data APIs, cron and worker services
Azure Database for PostgreSQL Flexible Server ×2The Hub database, and the shared server holding one database per project
Azure Key VaultSecrets, signing keys, OAuth tokens, the wildcard certificate
Azure Container RegistryApp images (built with ACR Tasks)
Storage accountStatic sites, source bundles, project buckets
Log AnalyticsLogs and the audit stream
Azure DNS zoneapps.<your-domain>, delegated once

The control plane runs in its own environment, separate from where apps run, so an app can't reach Hub internals over the network. Only the Hub's worker has rights to change resources, and only inside the managed resource group.

Planned setup​

  1. Deploy from Azure Marketplace (or a Service Catalog definition for testing).
  2. Admin consent. One consent link creates the Edge and MCP app registrations and grants the read-only Microsoft Graph permissions Org Sync needs (User.Read.All, GroupMember.Read.All).
  3. Pick admin groups, mapped to the Org Admin role.
  4. Pick a domain. Delegate apps.<your-domain> to the installed DNS zone, or start on a temporary vastframe-provided domain.
  5. Optional: connect the first integration, peer the network to on-premises systems, and deploy the Microsoft 365 Copilot agent.

The goal is under 30 minutes from Marketplace to the first deployed app.

Sign-in for a self-hosted install​

The organization signs in with your Microsoft Entra ID through one app registration. Only tokens from your own Entra tenant are accepted, and the Edge supports a client secret or a certificate credential.

The redirect URIs, token claims, settings and verification steps are in one place: Microsoft Entra ID (self-hosted).

Operations​

  • Upgrades: signed releases, applied by the Hub in your maintenance window.
  • Monitoring and backup: standard Azure tools; logs in Log Analytics; Postgres point-in-time restore.
  • Support access: customer-operated by default; optional just-in-time publisher access.
  • Usage reporting: the Hub reports usage itself, so nothing operational depends on vastframe's services.

Network exposure​

Chosen at install time; see Domains and network.

Was this page helpful?