The Azure Static Web Apps alternative
Everything you share with Azure Static Web Apps,
without the ARM template.
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.dev gives you company SSO on any HTML file. No Azure account. No infrastructure.
The demo shows an agent publishing a doc to display.dev – from a chat or a terminal – then the team opening its URL, commenting, the agent publishing v2 at the same URL, and the doc being shared with someone outside the company.
Cursor, Codex, Claude Code – any agent that writes a file. Switch agents anytime – your URLs, versions and comments stay put.
display.dev vs. Azure Static Web Apps
| display.dev | 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 | ❌ | ✅ |
The Azure auth problem
- Auth means Azure AD
- Azure SWA Standard is $9/app/month, but its authentication is built around Azure AD – so every viewer has to be in your tenant before they can open the page.
- Google Workspace companies pay twice
- Your people aren't in Azure AD by default. You either invite each viewer as a B2B guest or configure a custom OpenID Connect provider. That's IT work, and it repeats for every new reader.
- display.dev Pro includes both
- Google Workspace SSO and Microsoft 365 SSO, at €49/month flat. Google companies sign in with Google, Microsoft companies with Microsoft. Neither needs Azure.
Azure SWA is excellent – for Azure-native deployments
- Production single-page apps
- React, Angular or Vue deployed as real infrastructure, with Azure Functions behind them.
- Microsoft-shop pipelines
- Azure DevOps CI/CD and Azure AD already run your identity and your deploys.
- Long-lived deployments
- For permanent infrastructure in an Azure estate, SWA is well-integrated and cost-effective.
The overhead for sharing internal HTML files
Sharing one HTML file through Azure SWA is a 1–2 day project before anybody reads it, and every artifact after that either shares the repo or needs a new SWA resource.
With display.dev, dsp publish ./proposal.html returns the URL in about 15 seconds.
- ✗An Azure subscriptionStep zero if your team doesn't already have one.
- ✗A Static Web App resourceCreated through the Azure Portal or an ARM template.
- ✗A connected repositoryGitHub or Azure DevOps, plus the build and deploy workflow.
- ✗Authentication configured in the PortalSeparately from the deployment itself.
- ✗Viewers provisioned in Azure ADOr B2B guest invites, one per reader.
- ✗A CI run for every changePush to the repo and wait.
display.dev: publish anything, no infrastructure
https://acme.dsp.so/0kzNYG7O-q1-architecture. No git repo, no CI, no subscription.@yourcompany.com Google account. One click, no Azure AD, no guest provisioning.Pricing
Try it. No credit card.
- Included: 10 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Audit logs
For teams that need company auth.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: 90 days audit logs
For compliance-driven organizations.
From €499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: 365 days audit logs
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.
Try display.dev free
- €49/month flat – no Azure subscription, no Azure AD provisioning
- Google Workspace and Microsoft 365 SSO both included
- First artifact in 15 seconds · No credit card
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. The artifact stays the current version at the same URL, not a one-shot screenshot.
dsp publish ./file.html from your terminal, or one sentence in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Cursor, Codex, and Claude Code all work, along with any agent that creates HTML or Markdown output.
Common questions.
Does display.dev work if our company uses Microsoft 365?
Yes. display.dev Pro 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.
What if we already have Azure SWA deployed for our app – can we use display.dev alongside it?
Absolutely. Azure SWA for your production application, display.dev for sharing internal HTML artifacts. They're complementary, not competing.
Can display.dev replace our existing SWA setup?
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.dev is significantly simpler.
Is display.dev SOC 2 compliant?
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.
What about on-premises or Azure Government?
display.dev is hosted only – there's no on-premises or self-hosted deployment. For stricter compliance, Enterprise adds SAML, a signed DPA, and 365-day audit retention. If your requirement is that the vendor never holds the data, display.dev isn't the fit.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).

