Native macOS editor · open .deck format

Presentations built by you and your AI.

Your agent composes within templates. You refine the result in a real desktop app, and later agent passes preserve your adjustments.

Request early accessSee how it works

Private preview in development · Apple silicon Macs

Actual Decktype interface with slide navigator, canvas and inspector
The actual native macOS interface from the current development build.
Format
Open .deck file
Files
On your own drive
Platform
macOS Apple silicon
Exports
PDF and PNG
The product, without stagecraft

A real editor. Files you continue to own.

The canvas stays central, with the navigator on the left and inspector on the right. Work manually without an agent, then bring one in only when it adds value.

Native
A fast macOS application built for editing and presenting.
Local
.deck files remain on your drive and are readable outside Decktype.
Interoperable
PDF and PNG export; PowerPoint export that Keynote can open, depending on plan.
The .deck format contract

The agent composes. You decide. The file remembers both.

Templates expose structured slots to the agent. Your manual edits become explicit overrides, so a targeted regeneration does not start from scratch.

  1. 01

    Compose

    The agent fills template slots and builds the narrative.

  2. 02

    Refine

    Adjust text, position, color and charts directly in the app.

  3. 03

    Return

    The agent updates linked content without deleting human overrides.

One local file connects the agent’s passes to your edits.

Render proof

A complete deck, not an isolated demo.

Kairia Vision contains 22 slides produced by the same renderer as the app. Here is every one of them, from cover to close.

Kairia Vision 2026 · 22 slides

  1. Cover: AI in your teams, not in a slide
  2. The 2026 starting point, in one quote
  3. From 2022 to 2026: intelligence is climbing, fast
  4. 100 times cheaper than two years ago
  5. Agent anatomy: an LLM alone is not enough
  6. The three illusions of enterprise AI
  7. Conviction: hands in the code, not a slide
  8. Three non-negotiable pillars
  9. Kairia, AI integrator
  10. Method: four phases, from POC to installed workflow
  11. Upskilling is a deliverable
  12. Transverse, measurable levers
  13. Transverse positioning
  14. Case 01: software company, tech team at scale
  15. Case 02: consulting, transformed deliverables
  16. Before and after: what changes for your teams
  17. In-house tools: PilotRanker and SkillReg
  18. The R&D Velocity audit
  19. Frontier models by default, custom on demand
  20. Three reasons to start now
  21. Next step: map your AI workflows
  22. Closing and contact
Browse all 22 slides
Built for agents

Elsewhere, the agent asks. Here, it writes the document.

A .deck is a contract the agent writes directly: addressable slots in compact JSON, and an engine that guarantees the render. No intermediary AI interpreting instructions, no improvised layout.

One real 50-slide deck
.deck file29 KB
Equivalent PowerPoint417 KB

14×less data to describe the same deck. Measured, not estimated.

Deterministic
The agent addresses each slot precisely, and the engine renders the same slide on every pass. What is written is what appears.
Verifiable
The agent re-reads the file, validates the structure and reviews the render slide by slide. No black box between the agent and the result.
Control and reversibility

Your work does not depend on a browser.

A .deck is a structured local file. Version it, hand it to an agent, open it in the editor and deliver a PDF, PNG images or a PowerPoint file.

Templates and themes

Define the brand once, then compose within that system.

Native presenting

Present from the app, including on a secondary display.

Standard outputs

PDF and PNG for rendering; PowerPoint for continued client-side editing.

Privacy, precisely stated

Local by default is not a magic claim.

Decktype does not receive the contents of your local files. If you ask Claude, OpenAI or another provider to generate content, data sent to that provider follows its own terms and settings.

Read our security approach
Get started

Prepare for the private preview.

  1. 01

    Request access

    Tell us briefly about your use case and macOS setup.

  2. 02

    Prepare a real case

    Choose a deck or workflow you would like to test.

  3. 03

    Test with us

    Access opens progressively while the product is being finalized.

Private preview

Test Decktype before its public release.

Request early accessSee pricing

Private preview in development · Apple silicon Macs