How Do Thinkfree's Three SDKs Fit Together?

Updated

Thinkfree splits document handling into three composable SDKs that map to different stages of a document's lifecycle: creation and editing, processing and management, and auditing. You can adopt one SDK for a narrow task or combine all three to build a custom document workflow inside an application or AI agent. The right combination depends on whether you need to author files, operate on existing ones, or track what happened to them.

The three SDKs and their roles

Thinkfree describes its offering as "three composable SDKs, one document lifecycle," covering DOCX, XLSX, and PPTX files. The page groups them under a single heading — "Document infrastructure for applications and AI agents" — and frames the set as "document capabilities for production applications."

SDK Lifecycle stage What it handles
Creation / editing SDK Author Create and edit DOCX, XLSX, PPTX content
Processing / management SDK Operate Process, manage, and organize existing documents
Audit SDK Verify Audit document activity and state

The exact API surface of each SDK is not enumerated in the source material, so treat the table as the functional split Thinkfree advertises rather than a method-by-method reference.

How they compose

The page's "How the SDKs fit together" section implies the SDKs are designed to be layered rather than used as a single monolith. A practical reading of the lifecycle model:

  • Author — generate or modify a document (for example, an AI agent drafting a contract as DOCX).
  • Operate — run processing and management tasks on that file, such as search, retrieval, versioning, and locking.
  • Audit — record and inspect what happened to the document over time.

Because they are composable, you are not required to use all three. An app that only needs to produce files can take the creation SDK alone; a system that receives documents from elsewhere can start at the processing layer.

The lifecycle in practice

The page's code and diagram sections show the kind of operations the management layer covers. The excerpt illustrates a concurrent-editing scenario:

  • Search — find and retrieve documents (e.g., locating acme-contract.docx).
  • Versioning & locks — manage concurrent updates, with states like Locked v11 v12 v13 v14.
  • Save & release — commit the latest state, save a version, update metadata, refresh the index, and release the lock.

That sequence is a concrete example of why the SDKs are separated: locking and versioning are operational concerns that sit between authoring a file and auditing its history.

Choosing a combination

Use this as a decision guide:

  • Only need to generate or edit files? Take the creation/editing SDK.
  • Need to search, version, lock, or manage documents you already have? Add the processing/management SDK.
  • Need a record of document activity for compliance or review? Add the audit SDK.
  • Building an AI agent that drafts, stores, and tracks documents? Combine all three so the agent can author, operate, and verify within one workflow.

What to verify before committing

The source material confirms format coverage (DOCX, XLSX, PPTX) and the three-SDK structure, but does not list per-SDK endpoints, language bindings, or limits. Before choosing, check the pricing page for plan terms and confirm the specific SDK methods you need against Thinkfree's developer documentation.