The model in one screen
- One deck is one artifact. A deck is a folder of HTML pushed from the command line, and it lives in your account as one thing with a page of its own: the deck full-page under a bar where you rename it, duplicate it, share it, read its history and delete it. A push answers with that page. The deck is the artifact
- Every push is a version. Versions are immutable and numbered; unchanged files never upload twice; any version pulls back byte-exact. The owner sees the whole history, a recipient sees one version. Versions
- Links are made on top. A share link is a secret URL that opens the deck for whoever holds it, under a slim bar naming the deck, its version and its files, following the latest version or pinned to one, with its own switches (annotations, forms, file uploads, downloads, the bar), an expiry, a password, view counts and instant revocation. A link is public to anyone with its URL; a deck with no link is private. Share links
- Files travel with the version. Whatever you put in a
downloads/folder is the version’s attachment set, downloadable from the link one by one or as a zip, and switched off per link when a recipient should look but not take. Attachments - A sandboxed viewer. User HTML renders under
Content-Security-Policy: sandbox: an opaque origin with no cookies, no storage, no credentialed API (viewer security model). - Collaborators and reviewers. Per-deck grants for external people who push new versions of one deck, and annotator links whose notes land in the owner’s inbox.
- Agents as first-class users. The
slidelessCLI, the/mcpendpoint with 41slideless_tools, and scopedslk_API keys: every instance is agent-ready at boot.
Two ways to run it
- Antasphere cloud: slideless.antasphere.com, operated by
Antasphere. Sign in with your Antasphere account, one account managed at
account.antasphere.comand shared across every Antasphere tool. Organizations and membership live there too. See Your Antasphere account. - Self-hosted: one Docker image plus a Postgres container, running entirely on your own machine. All state lives in your database and one data volume; nothing phones home. Every instance is its own OAuth 2.1 authorization server and API-key issuer, so nothing works or breaks because of anyone else’s infrastructure. Start at Install.
Where to go next
- Connect an agent: the five-minute on-ramp, pointing a CLI or an MCP host at your instance.
- The concepts: the deck as an artifact, versions, share links and attachments, one page each.
- Your Antasphere account: how sign-in, organizations and the CLI work on the cloud edition.
- The Slideless CLI and the MCP connector: the two agent surfaces in full.
- Install, reverse proxy, deployment profiles and upgrades: run your own instance.
- Backup and restore and the scaling drill: operate it with confidence.
- Security posture and the viewer security model: what is enforced, and how untrusted HTML is contained.
- Environment reference: every variable.