Support and licensing

Start development with Build an editor product. This page describes package availability and support boundaries.

Choose by layer

Package or layer	Current license	Distribution
`@quirekit/core`, StarterKit, common extensions	MIT	Matching public releases or workspace dependencies
`@quirekit/dom-view`, `@quirekit/pm-*`	MIT	Native DOM and public core
`@quirekit/view`, `@quirekit/classic-editor`	AGPL-3.0-only	Commercial licensing is also available
`@quirekit/classic-docx`, Word packages, Classic Pro	Commercial	Obtain through the relevant distribution and license

The acquired package's LICENSE is authoritative. Core's MIT license does not cover every optional package. API license labels are generated from package metadata.

Classic product choices, free evaluation and community keys, paid product lines and key deployment are maintained in Classic documentation, free evaluation and community licenses and commercial use.

Scope

Core follows Tiptap extension authoring patterns; third-party plugins still need package-identity and view-assumption checks.
Native DOM examples demonstrate browser editing and commands, not Canvas pagination or Word round-trip verification.
Word conversion has its own support scope and diagnostics; this site does not promise complete Microsoft Word parity.
Collaboration, accounts, backend persistence and business permissions require host assembly and are not services provided here.
Alpha APIs may change. Pin versions and validate existing documents and custom extensions when upgrading.

Examples

Examples use real public APIs. JSON downloads capture current content; navigation or refresh does not automatically restore it. Source tabs and raw Markdown publish the same complete files.

A deployment can provide NUXT_PUBLIC_QUIREKIT_LICENSE_KEY for this site's Word experience. This does not grant access to commercial packages or replace the host application's licensing arrangements.