Thinkfree Document Editor SDK VS Nullstack

Thinkfree Document Editor SDK's answer

The client SDK is JavaScript, distributed on npm as @thinkfree.dev/tfo-sdk. The editor embeds into a host application through a standard iframe integration and exposes over 900+ object-level API methods.

Server-side, the SDK ships as Docker container images and runs on Docker. Cloud Office is integrated through REST API session issuance. Storage connects to host storage, Amazon S3 and S3-compatible object storage, WebDAV, or HTTP storage.

Thinkfree Document Editor SDK's answer

Most document SDKs handle either the file or the interface, not both. Thinkfree Document Editor SDK does both against a single open document. Application code and AI agents modify paragraphs, tables, ranges, and slides through object-level APIs, while users see and edit the same document in an embedded Office editor. There is no synchronization step between a programmatic copy and a user-facing copy.

The SDK also covers word processor, spreadsheet, and presentation editing in one integration, for DOCX, XLSX, PPTX, and ODF files.

Thinkfree Document Editor SDK's answer

Teams choose it when their product needs users to work with real Office files rather than a simplified representation of them. Rich text editors with a DOCX converter tend to flatten page breaks, sections, merged cells, and tracked changes. Server-side document libraries produce correct files but give users nothing to look at.

Thinkfree Document Editor SDK covers editing for word processor, spreadsheet, and presentation documents in one embedded editor, exposes the same document operations to an application's own LLM or AI agent, and deploys with Docker inside the customer's own infrastructure or through a managed cloud API. A free commercial tier is available for evaluation and small deployments.

Thinkfree Document Editor SDK's answer

Product and engineering teams that need Office document capabilities inside their own application rather than a separate office product.

This includes AI-native services in legal, finance, HR, and consulting that need a document canvas where both the user and the agent work on the same file. It also includes enterprise applications such as groupware, ERP, and PLM where users currently leave the product to open a document, and system integrators or ISVs that deliver document editing under their own brand inside a client environment.

Thinkfree Document Editor SDK's answer

Thinkfree released the world's first web-based office editor in 2000 and has developed document engine technology since. That engine has run in production inside other companies' products for years, as a complete office solution.

As AI systems began generating and revising documents, a different problem surfaced. A model can produce text, but an Office file is a structured artifact with formatting, tables, charts, and relationships that text alone does not reconstruct. Thinkfree opened the same engine as a developer SDK so applications and agents can operate on document objects directly, and users can review the result in the same editor. The SDK was previously offered as Thinkfree Office.