Skip to content

Give agents the right wayto work withreal documents.

AI agents can generate text and code. DeckFlow helps them understand, change, process, and deliver real editable documents without losing structure or fidelity.

DeckFlow is open-source document infrastructure for AI agents. Choose DeckUse, DeckOps, or HTML2Deck by the document task you need, then use Solutions when the work is already a presentation or document workflow.

Choose by taskUse a ready-to-use Solution
What are you trying to do?Choose by task
01Create, edit, or refine PowerPoint with AI.Create, edit, and refine PowerPoint.DeckUse02Turn complex documents into reliable knowledge.Build reliable knowledge from documents.DeckOps03Web-authored work must become editable PPTX or DOCX.Deliver web content as Office files.HTML2Deck
DeckUse and DeckOps are distinct runtimesHTML2Deck is an independent bridge

Start with the document task.

These are three Product paths for different jobs, not three levels of one tool. Technical detail becomes useful after the product choice is clear.

01
PowerPoint · lossless runtime

Create, edit, and refine PowerPoint with AI.

DeckUse is the lossless PowerPoint runtime for agents: controlled creation, explicit operations, validation, and recoverable edits. Current editing evidence is PPTX-scoped; Word and Excel are planned.

Best fit · PowerPoint creation, editing, and refinement
workspace / quarterly-review.pptx
  1. 01initidentify working document
  2. 02inspect / querylocate supported content
  3. 03applyexecute explicit operation
  4. 04validatecheck the intended result
  5. 05commitretain the next known state
Real release-scoped contract · illustrative document · evidence boundary required
02
Document intelligence · future-state

Turn complex documents into reliable knowledge.

DeckOps is the document intelligence pipeline for agents. Format-specific IR, reading order, Markdown/RAG, extraction, modification, and same-format export remain a future-state contract.

Best fit · structure-preserving knowledge from complex documents
Input
report.pdf

complex document

Future-state route
Parse to IR

format-specific contract

Result
reliable knowledge

with limits attached

Grounded explanatory artifact · future-state IR contract, not a released pipeline
03
Web content · editable document bridge

Web content in. Editable PPTX and DOCX out.

HTML2Deck turns web content into high-fidelity, editable PPTX and DOCX files—and turns documents back into shareable web pages. Current path: HTML/URL/stdin/SVG to PPTX or PNG. Testing: PPTX to web. Planned: dedicated DOCX routes.

Best fit · web-authored work that must become Office delivery
PPTXDOCXXLSX
Q3 operating review
deck.html
<main data-html2deck>  <h1>Q3 Review</h1>  <section>…</section></main>
Grounded explanatory artifact · Office formats, directions, and fidelity remain release-scoped

Two distinct runtimes, chosen by the job.

DeckUse and DeckOps are independent working models. They do not share one Runtime, API, or execution system.

How should the agent carry the work?Two product runtimes
When PowerPoint must stay editable and inspectable

DeckUse

A lossless PowerPoint runtime for controlled creation, repeated edits, and recoverable agent workflows.

  • Create and refineStart from a template or an existing deck
  • Apply explicit operationsMake scoped, reviewable changes
  • Validate and traceCheck the result before work continues
Choose DeckUse
When documents must become reliable knowledge

DeckOps

A future-state document-intelligence pipeline: format-specific IR, structure preservation, and downstream knowledge work.

  • Preserve structureKeep reading order before retrieval
  • Route to IRUse a format-specific parse path
  • Operate with limitsClaims stay release-scoped until proven
Choose DeckOps
Supporting capabilities stay product-owned
InspectProbe for bounded document evidence
RenderCreate visual representations for review

Each Product keeps its own model, interfaces, and evidence boundary.

Compare the execution models

Office files, meet the web.

HTML2Deck is the dedicated interoperability layer between Office documents and HTML. Current delivery is web content to PPTX or PNG; PPTX-to-web is testing and dedicated DOCX routes are planned.

View HTML2Deck usage
Office workspaceFamiliar files
Presentation.pptx
Document.docx
Workbook.xlsx
Quarterly operating review
PPTX → web · testing
HTML2Deck
HTML → PPTX/PNG · current
Browser workflowStructured HTML
deck.htmlHTML5
1<article>2 <h1>Quarterly review</h1>3 <section data-chart>…</section>4</article>
Quarterly review
Current · web content to PPTX or PNGHTML, URL, stdin, or SVG inputs become Office delivery files where supported.
Testing and planned directionsPPTX-to-web remains testing. Dedicated DOCX routes are planned, not current delivery.
Grounded explanatory · Office formats, conversion directions, editability, and fidelity remain release-specific

Need a presentation result now?

Translate, Generate, and Revamp are ready-to-use Solutions for existing presentation work. They are direct service entrances—not additional Products.

These services sit under Presentation Workflows. Document Automation, Document Intelligence, Document Governance, and Presentation Workflows remain the four job-led Solution families.

Explore all Solutions
Solution familyStart from the jobRoute without changing Product IA
Document Automation

Automate a document job with visible operations and results.

DeckUse, DeckOps, or HTML2Deck by the actual task.

Document Intelligence

Preserve structure before an agent reasons or acts.

DeckOps direction; DeckUse for current PowerPoint work.

Document Governance

Keep operations, evidence, and output inspectable.

DeckUse or DeckOps under their own lifecycle.

Presentation Workflows

Translate, generate, revamp, or deliver presentation work.

Use the services above; use HTML2Deck for web-authored delivery.

Frequently asked questions

Answers about DeckFlow Products, open source, formats, and pricing.

DeckFlow is open-source document infrastructure for AI agents. It gives agents three Product paths—DeckUse, DeckOps, and HTML2Deck—plus ready-to-use Solutions for presentation and document workflows.

Choose by the document task. DeckUse creates, edits, and refines PowerPoint. DeckOps turns complex documents into reliable knowledge under a future-state IR contract. HTML2Deck delivers current web-to-PPTX/PNG conversion, with PPTX-to-web testing and dedicated DOCX routes planned.

DeckUse is AGPL-3.0. DeckProbe and DeckRender are MIT. HTML2Deck is proprietary. DeckOps does not yet have an effective repository license on the public legacy repository.

DeckUse current reviewed behavior is scoped to existing PPTX. HTML2Deck current path converts HTML, URL, stdin, or SVG to PPTX or PNG. DeckOps remains a future-state product contract until a release proves format-specific IR claims.

DeckFlow uses one-time Credit packs. Credits pay for supported DeckUse, DeckOps, and HTML2Deck tasks as each Product's current release allows. See the pricing page for pack sizes.

No. Solutions are job-led workflows—such as translate, generate, and revamp—that run on the Product paths. They are not a separate Product layer.

Choose the Product. Then choose the interface.

Quickstarts, APIs, SDKs, CLI, source, examples, and Playground are adoption paths—not a second Product hierarchy. Only confirmed destinations enter implementation.

Explore developer paths