DeckFlow is open-source document infrastructure for AI agents, designed to enable agents to understand, modify, process, and deliver real editable documents without losing structure or fidelity. It addresses different document tasks through three independent product paths.
DeckUse is a lossless PowerPoint runtime for agents, used to create, edit, and refine PowerPoint. Its workflow is: initialize to identify the working document, inspect/query to locate supported content, apply to execute explicit operations, verify to check expected results, commit to preserve the next known state. The current editing evidence scope is limited to PPTX, with Word and Excel as planned features. DeckUse uses the AGPL-3.0 license.
DeckOps is a document intelligence pipeline for agents, designed to turn complex documents into reliable knowledge. It promises format-specific IR, reading order, Markdown/RAG, extraction, modification, and same-format export, but these are future-state contracts. DeckOps's public legacy repository currently has no valid license. DeckUse and DeckOps are two independent working models and do not share the same runtime, API, or execution system.
HTML2Deck is a dedicated interoperability layer between Office documents and HTML. Current delivery paths: HTML, URL, stdin, or SVG converted to PPTX or PNG; in testing: PPTX to web pages; planned: dedicated DOCX routing. HTML2Deck is proprietary software.
In addition, DeckFlow provides ready-to-use solutions for existing presentation work, including translation, generation, and transformation. These services belong to the presentation workflow and, together with document automation, document intelligence, and document governance, form four task-oriented solution series. Solutions are not an independent product layer, but workflows that run on the product paths.
For pricing, DeckFlow uses one-time Credit packs, and Credits are used to pay for supported DeckUse, DeckOps, and HTML2Deck tasks, depending on the support scope of each product's current version. See the pricing page for pack sizes.
Adoption paths include Quickstarts, API, SDK, CLI, source code, examples, and Playground, but they are not a second product layer.
