DeckSpace — presentations that are web pages, not slide files

What it is<br>See it<br>AI Enabled<br>About

DeckSpace

Presentations that are web pages, not slide files.

Describe your story in chat. DeckSpace builds the whole thing as one live<br>HTML page — in your own house style — and puts it at a URL instead of in an attachment.

Open the app →

The generation problem is solved. The delivery problem wasn't.

Ask any good model for a deck today and you get back a single HTML file that is often<br>better than what you'd have built by hand — real layout, live charts, no rectangle.<br>And then you're stuck. An .html file opens, and that is all it does.

What a file costs you

You can't fix a typo after sending it.

Nobody can reply on the slide they mean.

You can't present it to a room from a link.

It doesn't paste into Slack as anything.

What a link gives you

Update it after sending; the link is the same.

Comments land on the slide they're about.

Present from the URL, on any screen.

Paste it anywhere and it previews.

It keeps whatever shape the material wants

Some stories are slides you step through in a room. Some are a scrolling document you<br>read at a desk, with tables that don't fit on a slide and never should have. DeckSpace<br>decides from the material, and doesn't chop a report into slides to satisfy a format.

Slides<br>One view at a time, paced for a room, with a presenter mode and a progress bar.

Scrolling documents<br>One continuous page. Long tables, real paragraphs, chapters that are as long as they need to be.

Tabbed dashboards<br>Several views behind one link — like the page you're reading now.

See it

A real deck, running here

This is not a screenshot. It's a live deck served from DeckSpace's isolated viewer<br>origin, the same way every shared link is served — its own tabs, charts that draw<br>themselves from data embedded in the page, and a chart and table that refilter together.<br>Scroll it, switch its tabs, drag its scrubber.

Beyond Slides — a deck about what a deck can do, built as one HTML page.<br>Open it full-screen →

The numbers are computed, not typed

The model never writes a figure into a chart. It writes the question the chart is<br>asking, and the data travels inside the page — so a chart and its caption cannot<br>disagree, and a transposed digit is not a thing that can happen.

Data in the file<br>A deck fetches nothing at runtime. It works offline, and it can't leak where it's opened.

Sandboxed<br>Deck JavaScript runs on a separate origin and cannot reach your workspace.

Yours to edit<br>Change the words in place, or hand a slide back to your AI to redesign.

AI Enabled

Built with your AI, not instead of it

DeckSpace is the part after generation. You describe the deck; it composes the whole<br>thing in one pass — picking the slide count and the layouts rather than filling in<br>N fixed templates. That single difference is most of the quality gap.

Bring your own key. Anthropic or OpenAI, your account, your usage. Nothing is proxied<br>through ours, and we store the key encrypted.

Publish straight from the chat you're already in

DeckSpace speaks MCP — so the assistant that wrote your deck<br>can publish it into your workspace and hand you back a link, without a download and an<br>upload in between.

claude mcp add --transport http deckspace \<br>https://app.deckspace.org/mcp \<br>--header "Authorization: Bearer "<br>That command is for Claude Code. Claude chat and ChatGPT take a URL and<br>nothing else, so they use the connector form instead — no header to set:

https://app.deckspace.org/mcp/<br>In Claude chat , that goes in Settings → Connectors → Add custom connector. In<br>ChatGPT , enable Settings → Connectors → Advanced → Developer mode, then add it with<br>authentication set to No authentication — the token is already in the URL.

Your token comes from Settings → Publish once you have an account. Note<br>that in this form the URL is the credential, so treat it like a password; you can<br>rotate it from the same screen. ChatGPT's developer mode is beta, and on personal Plus/Pro<br>plans write actions like publishing may be restricted to Business/Enterprise/Edu — that's<br>a plan limit, not a broken setup.

Give it a house style once

Hand DeckSpace a deck your team already uses — HTML, .pptx, PDF or even a<br>screenshot — and it distils the palette, the fonts and the layout treatments, so what<br>comes out looks like your work instead of a template.

Try it with your own key →

About

Get in touch

Questions, bug reports, or a deck that came out wrong:<br>hello@deckspace.org. Real replies, usually same day.

What we do and don't collect

No analytics<br>No trackers, no ad pixels, no third-party scripts. The only cookie is the one that keeps you signed in.

Your keys, encrypted<br>AI API keys are stored encrypted and used only for your own requests.

Links are the sharing model<br>A shared deck is readable by anyone holding its link. Sharing is off until you turn it on.

Privacy · Terms