Azure Static Web Apps is built for deploying web applications in the Azure ecosystem. Using it to share HTML files with company auth means wiring up Azure AD, GitHub Actions, and ARM templates — for a file you want to share in the next 15 minutes. Display gives you company SSO on any HTML file. No Azure account. No infrastructure.
| Display | Azure SWA | |
|---|---|---|
| Monthly price (100 viewers) | $49 flat | $9/app + Azure AD costs |
| Setup time | 15 seconds | 1–2 days |
| Google Workspace SSO | ✅ Included | ❌ (Azure AD only) |
| Microsoft 365 SSO | ✅ Included | ✅ (Azure AD) |
| File upload (no git project) | ✅ | ❌ (requires git/pipeline) |
| CLI publish | ✅ (dsp publish) | ❌ (Azure CLI + SWA CLI) |
| Non-Azure viewers | ✅ | ⚠️ Requires Azure AD guest accounts |
| Unlimited viewers flat price | ✅ | ❌ (per-seat at scale) |
| MCP for Claude Desktop | ✅ | ❌ |
| Requires Azure subscription | ❌ | ✅ |
| Requires DevOps knowledge | ❌ | ✅ |
Azure Static Web Apps Standard tier costs $9/app/month. But authentication in Azure SWA is built around Azure AD — which means your viewers need to be in your Azure AD tenant.
If your viewers use Google Workspace, they're not in Azure AD by default. You'd need to either:
That's IT work, not a 15-second task. And every new viewer needs to be provisioned in Azure AD before they can access the page.
Display's Teams tier includes Google Workspace SSO and Microsoft 365 SSO — both, at $49/month flat. If your company uses Google, viewers authenticate with their company Google account. If you use Microsoft, they use Microsoft. No Azure required for either.
Azure Static Web Apps is the right tool when you are:
For permanent infrastructure deployments in a Microsoft shop, SWA is well-integrated and cost-effective.
Sharing an HTML file via Azure SWA requires:
That's 1–2 days of setup for the first artifact. And every new artifact either goes into the same repo or requires a new SWA resource.
With Display:
dsp publish ./proposal.html --name q1-architectureDisplay isn't a deployment platform. It's a publishing layer — the step between "file on disk" and "authenticated URL." You don't need a git repo, a CI pipeline, or an Azure subscription. You need an HTML file and 15 seconds.
For Google Workspace companies: Viewers authenticate with their @yourcompany.com Google account. One click. No Azure AD. No guest provisioning.
For Microsoft 365 companies: Same experience with Microsoft SSO. No Azure AD configuration beyond your existing M365 setup.
Free — one-time password auth, 50MB, unlimited viewers
Teams ($49/month) — Google + Microsoft SSO, 25GB, custom domain, unlimited viewers
Azure SWA Standard starts at $9/app/month — but authentication setup, Azure AD costs, and engineering time make the true cost significantly higher for the first internal sharing use case.
Publish your first artifact free →
Yes. Display Teams includes Microsoft 365 SSO — viewers sign in with their @yourcompany.com Microsoft account. No Azure AD configuration required beyond what's already in your M365 tenant.
Absolutely. Azure SWA for your production application, Display for sharing internal HTML artifacts. They're complementary, not competing.
For published web applications with CI/CD and backend functions — no, keep SWA. For sharing internal HTML files, reports, and artifacts with company auth — Display is significantly simpler.
SOC 2 Type II audit is on our roadmap. Cloudflare R2 (storage) and Postgres (metadata) are both SOC 2 certified. A DPA is available for Enterprise customers. See security for details.
Display Enterprise includes on-premises deployment options. Contact us for pricing and setup details.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Teams ($49/month flat).