Pricing.
Free core, paid add-ons.

Everyone who works on the parts of an Application that include or interact with the editor counts, on the client or server, even if only some call Domternal APIs. People working only on unrelated parts do not count. Developers are not named, but the 30-day rotation rule applies, and automated build systems are free. People who only execute existing tests do not count if they write or modify no test or Application code. People who write black-box tests solely through a finished Application interface also do not count if they do not modify the Application, its Domternal integration or build configuration, and their test code does not import or call Domternal Pro APIs. Team includes up to five Developers and can expand to fifteen. The plain-English license guide gives practical examples. Sections 4 and 12 of the license contain the exact definition and proportionate verification safeguards.

With annual billing, Team costs EUR 159 or USD 179 a month, billed as EUR 1,908 or USD 2,148 a year. With monthly billing, Team costs EUR 199 or USD 225 a month. For each Developer beyond the first five, annual billing costs EUR 28 or USD 32 a month, billed as EUR 336 or USD 384 a year. Monthly billing costs EUR 35 or USD 40 a month per additional Developer. Team supports up to fifteen Developers. So ten Developers is Team plus five, which is 3,588 euros a year (USD 4,068). Developers added part-way through a term are charged pro rata for the rest of it and then renew with the plan. For example, a Developer who joins with five months left in the term costs about five months, not twelve. The Order states every input and computes the exact amount by actual days. Developers you remove take effect at the next renewal. Past fifteen Developers it becomes an Enterprise conversation, priced on the shape of the deal rather than a per-Developer ladder.

No Domternal-hosted SaaS is required for the distributed product in a Customer deployment. Install the packages from the public npm registry and run them in infrastructure you select. The license validation and activation path has no Domternal service and sends us no document, comment, prompt, telemetry or usage data. The packages contain no hard-coded Domternal endpoint to which they automatically transmit application content or licensing data. That is also why the price counts only licensed developers rather than documents, end users or requests: there is nothing on our side to meter. Two parts do need an application endpoint. Real-time collaboration runs against a WebSocket server you configure, and the AI assistant calls whatever endpoint you configure, so data goes to the operator you selected under your arrangement with it. Both are covered in the self-hosting guide. The Domternal-operated playground is a separate website demo that explicitly configures our AI proxy, as the Privacy Policy discloses. We may later offer a separate optional hosted, managed or online product under its own disclosed price, terms and privacy notice. Choosing one would not silently add a hosted dependency, online activation or telemetry to packages already delivered under the offline model.

Install the packages from the public npm registry and evaluate them internally with no signup, no card and no fixed countdown, subject to the notice rules in License Section 5. Keyless evaluation is fully featured but displays evaluation notices in the editor and supported exports. Guarded headless and server-side evaluation requires explicit evaluation mode and may emit a warning. Production requires applicable Commercial rights and an active DMP2 Commercial Key. At our discretion, we may issue a time-limited Evaluation Key for a notice-free internal demo, normally for 14 days, but it never authorizes production. Evaluation includes no paid warranty, IP protection, support, SLA or Security Update commitment. See Installation and licensing.

Yes. Use the purchase route shown on the Team card: Polar Checkout when Buy Team is available, otherwise the request form below. Only an accepted first annual standard self-serve Team New Subscription Order that expressly states that it is eligible includes the limited 14-day voluntary money-back guarantee. The Refund Policy exclusively defines voluntary-guarantee eligibility, its deadline, covered fees, once-only rule, exclusions, required actions and request process. The license governs the effect of a refund on Software rights and keys. This summary does not create or expand eligibility, and mandatory rights remain unaffected.

When the Team card shows Buy Team, standard Team subscriptions use Polar Checkout. Polar acts as merchant of record and authorized reseller for payment, invoicing and tax, and its checkout records the billing cadence, currency and Developer quantity. After Polar records the Order as paid, we verify that record, generate the Domternal DMP2 Commercial Key and email it promptly to the checkout address on or after the actual Subscription start day. The browser success page alone is not proof of payment and never issues a key. Enterprise, OEM, multi-entity and custom purchases start with a conversation and use a directly accepted Order, usually followed by an invoice and bank transfer. Direct Orders use euros in Europe (the EEA, the UK and Switzerland) and US dollars elsewhere. Their final VAT treatment follows the accountant-approved rule for our and the customer's verified status. Cross-border EU business services use reverse charge only where it applies, including after validating the required VAT information. Otherwise, applicable law controls. Direct invoices are due in 14 days unless stated otherwise. A Subscription starts on payment or a later start date in its Order. Before a later start you can keep evaluating keylessly or request a separate Evaluation Key. The Terms of Service contain the complete ordering rules.

No. The current Product Line is Domternal Pro 1.x, and its machine-readable technical identifier in Orders, keys and package metadata is pro-1. Those are two names for the same Product Line, not separate products or charges. Each Order and Commercial Key cover only the Product Line identified in that Order. Renewals, Additional-Developer Orders, replacement keys and Security Updates do not add a future Product Line. A different Product Line requires a separate Order. The Commercial License Agreement contains the complete rules.

It may. The launch protection is precise: it runs for 24 months from the UTC day when the first Order for the root Subscription has both been accepted and fully paid, using the later day if those events differ. The base-plan charge and initial paid Developer quantity keep the prices in that Order while the same Customer and root Subscription continue with the same Product Line, plan, currency and billing cadence. Renewal payment received within the 14-day grace period preserves continuity. Additional Developers, add-ons, cadence or currency changes, another plan or Product Line, OEM or Enterprise scope, custom work, services, taxes and current transaction fees use the price in force when ordered. If you reduce the Developer quantity, protection for the removed quantity ends and later additions use the then-current price. The protection does not require us to keep a plan, cadence or Product Line available. After 24 months, after a longer lapse, or after a required attribute changes, a future Order or renewal uses the then-current price. No increase changes a running period that has already been paid.

For 14 UTC calendar days after the paid Subscription ends, a production deployment that already existed when the paid Subscription ended and any byte-for-byte identical Qualified Build may continue running and be deployed without code, dependency or feature changes. The grace period includes no continued development, new or modified build, new Application, feature release or ordinary support. After at least 12 consecutive fully paid and unrefunded months, exact Qualified Builds retain the perpetual runtime right defined in License Section 6(c), but development, rebuilding and new Applications still require an active Subscription except for the license's narrow express exceptions. Without that qualification, production ends after grace unless Section 7 applies.

The continuity rule is deliberately narrow. It applies only if we formally and permanently stop the entire Product Line and its commercial renewals, with no assignee or materially equivalent successor offering a commercially reasonable migration path. A rename, rebrand, new major generation, price or billing change, distribution change, business transfer with continuity, temporary interruption, or ordinary end of life with such a successor does not trigger it. An eligible Customer must be active or within the 14-day grace on the notice date, not suspended or terminated for breach, and current on due undisputed fees. Existing Qualified Build rights remain. A Customer without the 12-month qualification gets 90 days from notice to finish or migrate each Application demonstrably in production or active development before notice and retain one final artifact for each. No new Application may start. Afterward only those exact artifacts may run, be distributed or be redeployed, with no further development or rebuild except a key-only replacement allowed by the license. This creates no feature-release, ordinary-support or service-level promise. If we end prepaid obligations early, the unused prepaid portion is refunded.

Every commercial Product Line has one fixed Security Support End Date stated before purchase and in every Order. Domternal Pro 1.x ends on September 1, 2031 at 23:59:59 UTC. To the extent applicable mandatory law requires, necessary Security Updates for the unmodified Software are available without an additional license fee during that period. Except to the extent applicable mandatory law requires otherwise, an update does not, by itself, create or expand a production right, renew a Subscription or add ordinary support or an SLA, and the date is not restarted by a purchase, renewal, add-on or replacement key. See License Section 8 and the support page.

By email, with the response target of your plan. A target is the first substantive response, not a promised diagnosis or resolution, unless an Enterprise Order includes an express SLA. Ordinary support covers reasonable installation and basic-configuration questions for unmodified Domternal Pro in a documented supported environment, clarification of the documented API and behavior, and triage of a reproducible suspected defect using a minimal example. It does not include Customer application development or code review, architecture or security review, custom integrations or features, data restoration, migrations, training, legal or compliance advice, third-party provider or dependency support, or infrastructure debugging. Work outside scope may be declined or quoted separately. For fair use, we may combine related requests, prioritize by severity, Customer impact and order received, require sufficient reproduction details, pause while necessary information or access is missing, and limit abusive, repetitive or excessive volume disproportionate to the plan, without reducing an express Order SLA or mandatory-law obligation. Write from the address your license key was issued to, or name your company or order reference so we can match it. Bugs can also go on our public tracker if you prefer, but anything involving your own documents or data, and anything security related, should come by email instead. We may publish confirmed non-security defects and resolved issues in the Pro changelog, release notes, the tracker or another appropriate channel when useful. Those public channels are not a complete record of internal, duplicate, unconfirmed, immaterial, customer-specific or confidential matters. Security vulnerabilities follow coordinated private disclosure, subject to any earlier report, notice or disclosure required by law. Where applicable mandatory law requires individual notice, we may use the last notices address you provided. We may also publish or send an advisory when useful, but a voluntary notice does not create a duty to identify or contact every affected user or a continuing notification obligation. Details on the support page.

A paid Team Order includes the license warranty and the exclusive IP remedy in Section 10: for a covered third-party claim, we may obtain the needed rights, modify or replace the affected Software, or end the affected right and refund the applicable current-period prepaid fees. Team does not include a duty to defend or indemnify the Customer, pay its lawyers or cover third-party damages. An Enterprise Order may expressly add a negotiated IP defense or indemnity, process, exclusions and liability allocation at Enterprise pricing. Evaluation includes neither protection. Customer modifications, combinations not supplied or required by us, Customer specifications, third-party components, prohibited use, continued use after notice and failure to adopt an available replacement are excluded as Section 10 states.

Tell us what is missing before you walk away. Customer feedback informs product planning alongside product strategy, security, maintenance, technical feasibility and broader demand. A request or subscription does not promise delivery, timing or inclusion unless an accepted Enterprise Order states the commitment expressly. For non-contractual feedback, it costs one email. The Pro 1.0 announcement lists what shipped in the first release.

An accepted Enterprise Order can expressly add a Developer limit beyond 15, multi-entity or corporate-group scope, joint ventures, a service level agreement instead of response targets, procurement and security paperwork, negotiated IP defense and liability terms, or OEM rights. Enterprise may also fit a smaller team that needs one of those negotiated rights. None of those additions is automatic: the accepted Order identifies the applicable scope. It starts with a conversation rather than a checkout.

A standard Team Order covers one Customer named in the Order, whether a legal entity or a natural person buying for professional purposes. A controlled Affiliate can participate only as a negotiated exception that specifically names it in the accepted Order. Every Developer across the Customer, that Affiliate and contractors counts together under one limit, and the Customer remains responsible for compliance. Enterprise is the normal route for several entities, an entire corporate group, a joint venture or another multi-entity arrangement. The Order controls if it grants something different.

Almost certainly not. Building, deploying and operating your own applications is the ordinary license, including commercial SaaS, on unlimited servers and domains, with unlimited end users, and bundling the packages inside your own application is part of it. OEM is for three narrower cases: redistributing the packages on their own, putting them inside a product whose main purpose is to give our editor to other developers, such as an SDK, a component library or an editor toolkit, or a product whose main purpose is to let your own users embed the editor in software or sites they provide to third parties, such as a site or app builder. Sections 2 and 3 of the license draw the line.

The client does. Contractors and agencies count as Developers of the Customer whose Application they are building, so the license sits with the client rather than with you. A standard Team Order covers one Customer named in the Order, whether a legal entity or a natural person buying for professional purposes, not all of an agency's clients. If you build for several clients, each needs its own Order unless a custom Order expressly grants broader scope. Section 3(d) of the license.

Tiptap's public Start, Team and Business plans are a managed Cloud platform with included developer, environment and Cloud document allocations. Additional developer seats and Cloud document capacity are available as paid add-ons, and eligible plan cards allow more environments. Its on-premises option is a custom Enterprise agreement. Domternal Team is self-hosted software at a published price with no document, environment or request limits, and all six paid feature areas are included. The Tiptap vs Domternal comparison puts plan levels, features and prices side by side, checked against Tiptap's own pages. If you are evaluating CKEditor, the CKEditor vs Domternal comparison separates its GPL, public cloud and commercial self-hosting paths before comparing price.

Yes. Every version of the core editor, all four framework wrappers and 70+ extensions already published under MIT remains free under that license forever. Pro is a set of separate add-on packages on top. This describes already-published MIT releases, not the license of future releases that do not yet exist. The Free vs Pro guide compares the complete feature and licensing boundaries.