# Antasphere Documentation > Documentation for the Antasphere tool ecosystem: one account, every tool. > Each section below covers one product. Generated by sync/sync.mjs — do not edit. ## Antasphere - [Antasphere](https://docs.antasphere.com/antasphere/index): One account for every Antasphere tool: sign in once at account.antasphere.com and you are connected everywhere. Every tool in the family recognises the same identity, the same… - [Slideless](https://docs.antasphere.com/antasphere/tools/slideless): Slideless is the home for what your agents build. Agents produce HTML: presentations, small apps, plans, reports. Slideless keeps each one as a deck in your account, versioned on… - [CLI](https://docs.antasphere.com/antasphere/agents/cli): antasphere is the command-line client for your Antasphere account. One antasphere login signs you in with a code sent to your email and stores a personal API key in a local… - [Connecting agents (MCP)](https://docs.antasphere.com/antasphere/agents/mcp-connector): Your Antasphere account is reachable by agents over MCP at https://account.antasphere.com/mcp, protected by the account service's own OAuth sign-in. Nothing to install and no… - [Changelog](https://docs.antasphere.com/antasphere/changelog): Release history for Antasphere. ## Slideless - [Slideless](https://docs.antasphere.com/slideless/index): Slideless is the home for what your agents build. Agents produce HTML: presentations, small apps, plans, reports. Slideless keeps each one as a deck in your account, versioned on… - [Connect an agent to your instance](https://docs.antasphere.com/slideless/getting-started/connect-an-agent): Agents are the primary authors on a Slideless instance — this is the on-ramp for pointing one at yours. There are two surfaces, both self-contained on your box: - [Your Antasphere account](https://docs.antasphere.com/slideless/getting-started/antasphere-account): On Slideless cloud (slideless.antasphere.com) you sign in with your Antasphere account — one account, managed at account.antasphere.com, that works across every Antasphere cloud… - [The deck is the artifact](https://docs.antasphere.com/slideless/concepts/artifact): A deck is one artifact in your account: one record with a page of its own, a history of immutable versions, and share links created on top of it. Everything you do to a deck… - [Versions](https://docs.antasphere.com/slideless/concepts/versions): Every push is a new version of the deck, numbered from 1, and a version never changes once it is committed. The owner keeps the whole history and can show, pull or duplicate any… - [Share links](https://docs.antasphere.com/slideless/concepts/links): A share link is a secret URL created on top of a deck. Whoever holds it opens the deck: there is no sign-in on the other side, no visibility setting, and no way to make a link… - [Attachments](https://docs.antasphere.com/slideless/concepts/attachments): Files can travel with a deck: the spreadsheet behind a chart, the PDF of the slides, the raw data. Put them in a downloads/ folder at the root of the deck and push. Every file in… - [The Slideless CLI](https://docs.antasphere.com/slideless/agents/cli): slideless is the typed command-line client for a Slideless instance — the primary human/agent face of it. It signs in over email OTP (minting its own API key), pushes deck folders… - [The MCP connector](https://docs.antasphere.com/slideless/agents/mcp-connector): Every instance is MCP-capable at boot: the monolith serves a streamable-HTTP MCP endpoint at /mcp, protected by the instance's own built-in OAuth 2.1 authorization server. No… - [Deck self-description: metadata + AGENT.md](https://docs.antasphere.com/slideless/agents/deck-self-description): A deck can describe itself through two complementary channels: - [Annotations](https://docs.antasphere.com/slideless/sharing/annotations): Annotator share links let reviewers leave notes directly on a shared deck — anchored to the exact text, spot, or region they mark — and give the owner one place to read, resolve,… - [Forms](https://docs.antasphere.com/slideless/sharing/forms): A deck can collect answers, not just show slides. Write a plain HTML form in the deck, mark it with one attribute, and every share link serves it live: viewers fill it in right… - [Downloads](https://docs.antasphere.com/slideless/sharing/downloads): A deck can carry files that travel with it: a spreadsheet next to the report, the PDF of the slides, the raw data behind a chart. Put them in a downloads/ folder at the root of… - [Embedding decks on your site](https://docs.antasphere.com/slideless/sharing/embedding): Any share link can render inline on your own website — a landing page, a documentation site, an internal wiki — instead of sending visitors away to the viewer. Paste a small… - [Link analytics](https://docs.antasphere.com/slideless/sharing/link-analytics): Every share link already counts its opens (the _Views_ column next to each link). Link analytics goes one level deeper: each counted view is also recorded as its own event, so you… - [Install](https://docs.antasphere.com/slideless/self-hosting/install): For a dedicated Hostinger VPS with automatic HTTPS and setup through hPanel, follow Install on Hostinger. - [Install on Hostinger](https://docs.antasphere.com/slideless/self-hosting/hostinger): Run Slideless on a dedicated Hostinger VPS. You manage the VPS and its DNS; the template installs Slideless, PostgreSQL, and Caddy for automatic HTTPS. No terminal commands are… - [Reverse proxy (TLS)](https://docs.antasphere.com/slideless/self-hosting/reverse-proxy): TLS terminates at a reverse proxy in front of the app — documented, not bundled. Caddy is the recommended proxy: automatic Let's Encrypt, two lines of config. - [Deployment profiles](https://docs.antasphere.com/slideless/self-hosting/deployment-profiles): One template, one statelessness invariant, two documented shapes. Scaling is a deployment choice, not an architecture change: the app container holds no state (sessions in… - [Upgrade](https://docs.antasphere.com/slideless/self-hosting/upgrade): Upgrading a self-hosted instance is one command; data survives in the Docker volumes and migrations apply themselves at boot. - [Backup and restore](https://docs.antasphere.com/slideless/operations/backup-restore): What to back up on a self-hosted instance, how to automate dailies, how to restore — and the drill that proves your backups actually work. - [Scaling drill — proving Profile B](https://docs.antasphere.com/slideless/operations/scaling): deployment-profiles.md claims the image scales horizontally because the app container holds no state. Claims rot; this drill is the executable proof. It stands up real… - [Security posture](https://docs.antasphere.com/slideless/security/security): What a Slideless instance enforces out of the box, what its operator is responsible for, and the rules that govern rendering user content. - [The viewer security model (for operators)](https://docs.antasphere.com/slideless/security/viewer-security-model): Slideless's whole point is rendering untrusted, user-authored HTML to anonymous visitors. This page is what an operator needs to know about how that is made safe, what the… - [Environment reference](https://docs.antasphere.com/slideless/reference/env-reference): Generated from the zod env schema (apps/server/src/env.ts) — do not edit by hand; run pnpm --filter @slideless/server docs:env after changing the schema. The app refuses to boot… - [Changelog](https://docs.antasphere.com/slideless/changelog): Release history for Slideless.