The full inventory
Everything that is already in there
What Deckyard does today, grouped by the moment you need it, with the documentation one link away.
Making a deck
You pick a type and fill in the fields
There is no canvas and no text box to place. Every slide is a declared type with named fields, so the design was decided once, in the theme, and never again per slide.
Editing docs
-
34 declared slide types
A timeline, a matrix, a funnel, a quote, a chart. You choose the one you mean instead of drawing it.
-
The editor is a form
Title, subheading, byline, the items in the list. Fields with names, next to a preview that updates while you type.
-
A slide library
Save a slide you will need again, for yourself or for the team, and drop it into the next deck.
-
An image library
Uploads land in one searchable place instead of inside whichever deck happened to be open.
-
One deck, several languages
A deck carries its languages side by side and the viewer switches between them, rather than being copied and diverging.
Your brand
The house style is a file, not a habit
Colours, fonts, logos and layout rules are a theme: one JSON file, versioned like anything else. Nobody applies it, because there is no unstyled state to forget.
Theme docs-
A theme is JSON
Readable, diffable and reviewable. A brand change is a pull request rather than a new template nobody downloads.
-
On brand by default
A deck renders in the theme it was given. There is nothing to apply afterwards and nothing to forget.
-
Rebrand centrally
Change the theme and every deck using it follows, including the ones that are already published.
-
Your own licensed fonts
Upload the files once. Exports carry them inline instead of fetching them from somebody else’s font CDN.
-
A fork keeps its own
Custom themes live beside the shipped ones and take precedence, so a house style is never a patch to the core.
AI
On your key, inside the shape
AI is switched on by you, paid for by you, and confined to filling in fields that already have a declared shape. There is no model in the middle you did not pick.
AI docs
-
Bring your own key
You choose the provider and pay them directly. Turn it off entirely and the rest of the platform is unaffected.
-
It fills in, it does not design
A model asks which types exist and completes one of them. There is no layout for it to invent.
-
A draft from your notes
Paste what you have and it comes back as typed slides, which you then correct field by field.
-
Alt text and translation
The two jobs that never get done by hand, offered per slide rather than as a batch nobody reviews.
-
Drive it from your own tools
An MCP server exposes the same operations, so an agent you already run can write into Deckyard.
Working together
More than one person, without a merge conflict
Decks are usually written by a few people under time pressure. That means real permissions, comments where the slide is, and a way back to what it said yesterday.
Collaboration docs
-
Permissions per person
View, comment or edit, decided per deck, rather than one link that hands over everything at once.
-
Comments on the slide
Reply, resolve and delete, beside the live preview instead of in a separate thread that loses its subject.
-
Editing at the same time
Two people in one deck without overwriting each other, and without anybody having to announce it first.
-
Version history
Every save is a version you can read and restore, so “put back what it said this morning” is a click.
-
Activity and mentions
A notification when somebody changes or mentions something you own, instead of finding out during the meeting.
In the room
The audience answers on the slide itself
A question to the room is a slide type like any other, so the answers are part of the deck rather than a second tool you also had to open.
Presenter docs
-
Polls and scales
Multiple choice, multi-select, rating and Likert, answered from the room while the slide is on the wall.
-
Moderated Q&A
Questions arrive in a queue you decide to show. Nothing reaches the screen because somebody typed it.
-
Feedback and lead capture
Ask for a reaction or an address on the slide, and keep the answers with the deck they belong to.
-
Presenter view
Notes, the next slide, a timer, per-slide pacing and a highlighter, in a second window your audience never sees.
-
Follow along on a phone
A code puts the deck in the room’s own hands, in their language, with the question box attached.
-
Per-slide analytics
Afterwards: which slide people stayed on, and which one they actually answered.
Getting it out again
Six exits, none of them a request
A deck leaves in the shape you need it: a link, an embed, a single file, or a document for a tool that is not this one. All of it at any moment, without asking anyone.
Publishing docs
-
Publish with a link
One click, a readable URL you can edit afterwards, and a share image generated for it.
-
Private links with rules
Password, expiry date, e-mail verification, view or edit. Set per link, so revoking one does not revoke the deck.
-
Embed in your own page
The SDK resolves a published deck against your instance, and the polls and Q&A keep working inside the frame.
-
One self-contained HTML file
Fonts, images and the viewer inlined. It runs from any static host, or from a file on a stick.
-
PDF, PowerPoint, PNG, JSON
Four document formats out, including the JSON the deck was already stored as.
-
Feeds and share images
A published deck brings its own preview image, and a set of them can be an RSS feed.
And you are the one running it
One Docker Compose file, Node and Postgres. On your own servers under your own rules, or on an instance we run for you.