Skip to content
Product // Scope

What Lumdeck does and does not do

An honest list, so you can decide before you sign up. Last reviewed 3 October 2026.

What Lumdeck does

  • Hosts interactive HTML decks: a single HTML file or a zip with an index.html, from AI tools, Marp, Slidev, reveal.js or written by hand. Every upload is checked against published rules and version retention follows your plan: Free keeps the latest 3, Pro 20, and Team all versions. Older non-current versions are automatically pruned after uploads; a pinned share link does not protect a version from pruning. Keep your own originals.
  • Runs every deck in a sandbox on a separate web address, so a deck cannot read your account, its viewers' cookies or the page around it.
  • Shares decks with people who have no account: anyone-with-the-link, password, e-mail code or named people, with expiry, view limits and revoke.
  • On Pro and Team, lets a link be embedded on the websites you name. Every other site is refused. Free links cannot be embedded.
  • Presents full screen and runs live sessions where viewers follow your slides on their own screens.
  • Counts views without cookies and respects Do Not Track. Pro and Team add aggregate slide engagement; Team adds view totals and average time per share link. Slide engagement is not broken down by individual link or person.
  • Organises decks in workspaces with owner, admin, editor and viewer roles.
  • Lets AI agents and scripts publish through a REST API and a remote MCP server, on plans that include them.
  • Lets you download your data and delete your account yourself.

What Lumdeck does not do yet

Each item below is a deliberate choice for now, not an oversight. If one of them matters to you, tell us: it changes what we build next.

No malware scanning of uploads

Uploads are not scanned by an antivirus engine. Instead, executables, server scripts, nested archives, encrypted zips and files whose content contradicts their extension are refused, and every deck runs in the sandbox described above, on its own address, without access to cookies or storage. Allowing downloads of a deck's original file is off by default. Downloaded originals retain unmodified code and lose the hosted sandbox, CSP and network restrictions when opened elsewhere. Only open source you trust. A scanner is planned before we offer contracts that require one.

No watermark on viewed decks

Lumdeck does not stamp the viewer's name or address on slides. A watermark drawn over an HTML deck can be removed by anyone who opens the browser's developer tools, so it would promise protection it cannot give. To control who sees a deck, use e-mail-gated links, named people, expiry, view limits and revoke, and use Team link totals to compare labelled audiences. An anonymous view does not identify a person.

No right-to-left interface

The Lumdeck interface is in English and laid out left to right. Decks written in Arabic, Hebrew or another right-to-left language display exactly as their HTML is written, because Lumdeck shows the deck's own page unchanged; only the surrounding interface is not translated or mirrored.

No access check on every single request

When someone opens a deck, Lumdeck checks the link or their membership once and gives their browser a short-lived signed pass for that version. The pages and files of the deck are then served against that pass without asking the database again, which keeps decks fast and keeps the viewer separate from your account data. A revoked link, or a deck moved to the trash or taken down, stops loading in the viewer within 30 seconds. A link that has expired or used up its views refuses new openings at once; someone who already has it open loses it within 15 minutes. A removed workspace member loses access within 15 minutes.

Other things Lumdeck does not do

  • Edit or create slides. Lumdeck hosts and shares decks; you make them in your AI tool or framework.
  • Convert PowerPoint, Keynote, Google Slides or PDF. Export those to HTML first, or share them with their own tools.
  • Per-folder permissions. Roles apply to the whole workspace; a deck is visible to the workspace or only to the people invited.
  • Single sign-on (SAML) or user provisioning (SCIM). Sign-in is by e-mail and password or Google.
  • A choice of data region. Where data is stored is stated in the privacy notice; you cannot pick a region per workspace.
  • A service-level agreement. There is no uptime commitment or credit scheme yet.
  • Multi-page bundles with a manifest. A deck has one entry page, index.html; it can link to other pages inside the zip.

How this page is kept

This page changes in the same release as the product. When an item above is built, it moves to the first list and the changelog says so.