Skip to main content

Platform status

vastframe is in early access. The features in these docs are implemented and covered by end-to-end tests on the local stack, where local drivers stand in for Azure services and local stand-ins replace Microsoft 365, Teams and Salesforce. This page tracks which pieces still need their Azure or real-vendor implementation.

Feature status​

AreaLocal stackAzure / real vendor
Deploy loop: detect, build, run, previews, rollbackAvailableComing soon (ACR Tasks, Container Apps)
Edge sign-in, access rules, X-TC-UserAvailableComing soon (real Entra tenant, wildcard certificates)
Database, Data API, Studio, RLS helpersAvailableComing soon (Postgres Flexible Server with Entra auth)
Org Sync, org tree, cost, Hub roles, lifecycleAvailable (fixture directory, synthetic cost)Coming soon (Graph delta sync, Cost Management)
Integrations, grants, access requests, policiesAvailable (mock Graph, Salesforce, Teams, ERP)Coming soon (Graph on-behalf-of, Bot Framework, Salesforce Connected App, SQL Server over VNet)
Cron and worker servicesAvailableComing soon (Container Apps jobs)
Env vars and secretsAvailable (local encryption)Coming soon (Key Vault)
Storage: buckets, signed URLs, quotasAvailable (Azurite)Coming soon (managed identity, private endpoint)
Multi-tenancy, licences, installation APIAvailableHosted tenants in early access
Email-link accounts, People and GroupsAvailable (email to a local inbox)Coming soon (Azure Communication Services email)
Bring-your-own sign-in: Entra, OIDC, WorkOS SSO and SCIMAvailable (mock WorkOS)WorkOS works with a real account by configuration
Azure Managed Application and setup wizardn/aComing soon
OAuth sign-in for MCP clients and the CLIn/aComing soon (development token today)

Not built yet​

These appear in vastframe's design but aren't available. The docs don't describe them as features:

  • Custom domains per project (the Settings page shows the DNS records only).
  • Database backups and "restore to a new database" in the console.
  • A "view as user" preview for testing row-level security.
  • Teams tabs and Teams single sign-on inside the Teams client.
  • Graph change-notification triggers ("when a file changes, run a job").
  • Bring-your-own-git pipeline tasks (GitHub Action, Azure Pipelines).
  • Agents as a service type (kind: agent), approval-gated writes in the gateway's MCP surface, and the Microsoft 365 Copilot agent package.
  • Promotion to production gated by access requests.

Known limits​

  • One web, api or static service per project; any number of cron and worker services.
  • The Salesforce allowlist covers plain SELECT … FROM queries (no sub-queries).
  • ERP SQL is read-only and needs schema-qualified table names.
  • Worker services are started but not health-checked.
  • Environment-variable changes need a redeploy (by design).
  • Directory changes reach live access rules after the next Org Sync (every 5 minutes, or Sync now).
Was this page helpful?