--- url: /static-app-alternative title: Static.app Alternative with Company Auth priority: P2 keyword: static.app alternative secondary_keywords: static app vs display.dev, drag and drop static hosting sso, upload zip website private, static site hosting company auth funnel_stage: Decision schema: FAQPage, SoftwareApplication hero_style: routes hero_eyebrow: The Static.app alternative with company auth hero_routes: fileLabel: Route 02 – drop the file fileHeading: Publish one file, not a bundle. fileBody: One HTML or Markdown file. Anonymous publishing takes up to 50 MB. No archive to build, no folder to zip, no sync app to install. dropHeadline: Drop your .html file here dropSub: or choose a file foot: Either route returns a URL and a claim link. Claim it and you decide who can open it – anyone, named people, or your whole company. hero_rotator: prefix: - Everything you upload to Static.app, - without the words: - zip archive. - desktop app. - public site. - sync folder. suffix: "" section_layouts: A site host answers a different question: problem Who can open it: access description: "Static.app hosts a dragged-in archive as a public static site. display.dev publishes a single HTML file to a URL gated by your company's Google or Microsoft sign-in." --- # Everything you upload to Static.app, without the zip archive. Static.app is a one-click host for static sites: drag in an archive or a folder, get it live, edit in the browser, sync from a desktop app. display.dev is smaller on purpose. One HTML or Markdown file, no archive, and a URL whose audience you choose – anyone, named email addresses, or everyone at your company. [Try display.dev free →](https://app.display.dev) · [See pricing](/pricing) --- ## What Static.app does Its own line is "Drag-n-drop an archive with your page or a website and we will take care of the rest". Around that sit an in-browser code editor, desktop sync apps for Mac and Windows, GitHub Actions deployment, a REST API and an MCP server for connecting agents. It is a competent site host with a real programmatic surface. What it is not is an access-control product: the sites it serves are public, and there is no company identity to attach to them. Facts about Static.app are from `static.app`, captured 10 August 2026. --- ## display.dev vs. Static.app | | display.dev | Static.app | | -------------------------------------- | ----------------- | ----------------- | | Drag-and-drop to a URL | ✅ | ✅ | | Publish a single file, no archive | ✅ | Archive or folder | | Publish with no account | ✅ | ❌ | | Publish from an agent | ✅ (CLI, API, MCP) | ✅ (REST API, MCP) | | Restrict to named email addresses | ✅ | ❌ | | Google + Microsoft SSO | ✅ (Pro) | ❌ | | Who viewed it | ✅ | Not verified | | Inline comments an agent can read back | ✅ | ❌ | | In-browser code editor | ❌ | ✅ | | Desktop sync app | ❌ | ✅ | | Multi-page site with assets | Directory publish | ✅ | --- ## When Static.app is the right tool **A real multi-page site.** Several pages, images, stylesheets, a folder structure you want preserved. That is what it is for. **Editing after the fact, in the browser.** Its code editor means you can fix a typo without re-zipping and re-uploading. **Keeping a local folder in sync.** The desktop app is a genuine convenience if a site is something you maintain rather than publish once. Its REST API, MCP server and GitHub Actions integration cover the automated path too. --- ## A site host answers a different question Most agent output is one self-contained file, read by a handful of named people, and then either updated or forgotten. A site host optimises for the opposite: many files, many readers, kept live indefinitely. - **Zip, upload, unzip** – Ceremony around a document that was already one file. - **Public by construction** – A static site is served to whoever asks for it. - **No viewer list** – No sign-in, so no record of who read the analysis. --- ## Who can open it **Anyone with the link.** An open URL, served with noindex, when the content is genuinely public. **Invited people.** Named email addresses only, each with a one-time password by email. Per person, and removable per person. **Everyone at your company.** On Pro, Google Workspace or Microsoft Entra ID decides. Offboarding closes the page without anyone rotating anything. **Publishing is one command.** `dsp publish ./report.html`, an API call, or an MCP tool call from your agent. `dsp publish ./site/` handles a directory when you do need assets. --- ## Pricing **Free** – €0. 10 gated artifacts, unlimited public links, one-time password auth, unlimited viewers. **Solo** – €15/mo. Unlimited gated artifacts, 1GB storage, version history. **Pro** – €49/mo. Google + Microsoft SSO, private artifacts, 25GB, audit logs, unlimited viewers. **Enterprise** – from €499/mo. SAML, custom domain, RBAC, 365-day audit, DPA + SLA. [See all pricing →](/pricing) --- ## Try display.dev free - **One file, no archive** – and a visibility setting on the artifact - Publish from Cursor, Codex, Claude Code or any other agent - First artifact in 15 seconds · No credit card [Publish your first artifact free →](https://app.display.dev) · [See all pricing](/pricing) --- ## FAQ **Can display.dev host a multi-page site?** `dsp publish ./site/` publishes a directory with its assets, which covers a rendered docs build or a report with images. It is not a site platform though – there is no build step, no routing configuration and no functions. **Do I need to zip anything?** No. A single `.html` or `.md` file is the unit. Drop it, or point the CLI at it. **Can I edit the page after publishing?** You publish a new version at the same URL, from the agent or the CLI. There is no in-browser code editor; if editing in place matters to you, Static.app does that and we do not. **Is there a free tier?** Yes, and anonymous publishing needs no account at all – you get a URL and a one-time claim link back. **Will my page be public?** Only if you choose that. The other options are named email addresses or your whole company via SSO.