What an order says, and what signing it means.
Every production license starts with an order. We prepare and sign it first, an owner of your organization signs it in the console, and both of us keep the PDF. This page walks through what each order states, the standard wording it prints, and the rules behind the numbers. The License Terms incorporate it, so it is part of what you sign.
What an order is
An order form (an "Order") is the document in which PulsePoint Systems, LLC, trading as Kernstra ("Kernstra"), and the customer named in it agree the commercial terms of a license. Each Order states its number (in the form KS-OF-NNNN), the date it was prepared and the date until which it may be signed, thirty (30) days after Kernstra signs it. This page is the standard order terms that the License Terms incorporate, in the version in force on the day the Order is signed.
Kernstra signs an Order first. It binds both parties when an owner of the customer's organization signs it in the console before it expires. An unsigned Order lapses at the end of its last valid day. Kernstra may withdraw an Order that has not been signed, and tells the customer why. A signed Order cannot be withdrawn; it ends only as it and the License Terms provide, except that a signed Order not yet paid is void if the customer's organization is closed, and a signed upgrade or package to be paid by card that is not paid before the offer expires lapses.
Who signs
The Order names Kernstra's legal entity and the customer as its billing details state them (legal name and address). The person who signs it for the customer confirms that they are authorized to bind the customer, including to agree to the dispute resolution clause in Section 13.3 of the License Terms, and that they have read the License Terms, and gives their name and job title, which the Order prints. Kernstra keeps a record of each signature with its time, IP address and browser, as evidence of the agreement, as the Privacy Policy describes.
The license it grants
An Order for a license states: the product; the name of the customer's Application; its audience, printed as "Customer's internal staff", "Customer's customers and the public", or both, which the License Terms define as the Internal Audience and the Public Audience; the Monthly Users the fee covers; the domains on which its production key works (with their subdomains only where the Order says so) or, for an Application without a domain, the product and platform the Order describes, and any staging hosts; the plan and the features it includes, with any add-ons; whether the license is online (the SDK checks the license with Kernstra when it starts, when its key changes, and when a document is opened more than an hour after the last confirmed answer) or offline (it works without internet for a 12-month term); and whether it is billed on its own or as part of a package. Going over the Monthly Users an Order states never blocks the Application; Section 7.5 of the License Terms says what happens instead.
Fees and the first charge
The Order states the fee in US dollars per billing period (monthly, quarterly or yearly), excluding taxes, plus any tax Kernstra must collect under Section 7.2 of the License Terms, and how the first charge is made: either charged to the customer's card when the Order is signed, or invoiced when the Order is signed and due within thirty (30) days. Every license of an organization is billed on the organization's billing date, every billing period. The first charge of a license that joins later covers the time to that date (for a yearly license with less than sixty (60) days to it, a full year to the billing date after it), and a package's first charge is reduced by any credit for licenses moving into it. Those amounts are shown in the console when the Order is signed; where the Order prints a full period's fee as the first charge, the amount the console shows is the one charged. For a customer in the European Union or the United Kingdom, the Order states the customer's VAT identification number and the customer accounts for VAT under the reverse charge; without a valid one, Kernstra may decline the Order or, where it is registered to do so, add VAT to the fee.
Term, renewal and cancellation
Online license. It starts when the first charge succeeds (under invoice billing, when the Order is signed) and renews automatically every billing period. The customer may cancel it at any time in the console, and it stays active until the end of the paid period. Kernstra may cancel it, or decide at its yearly review not to continue it, only as Section 7.3 of the License Terms provides: with at least thirty (30) days' notice, effective at the end of the first paid period after the notice period, and, for a term of twelve (12) months or longer, only at the end of a term, with at least ninety (90) days' notice.
Offline license. It runs for twelve (12) months from when the first charge succeeds, billed as the Order states, and renews for further twelve-month terms unless either party cancels it before the term ends. Its key works until the end of the term, with the short technical period after it that Section 7.3 of the License Terms describes.
Package. It runs for twelve (12) months from when the first charge succeeds (longer when that charge covered more) and renews automatically for another twelve (12) months unless the customer turns auto-renewal off at least thirty (30) days before the term ends; without renewal, the package and every Application in it end with the term.
For a term of twelve (12) months or longer that renews automatically, Kernstra emails the renewal date, the amount and a link to cancel at least fifteen (15) and not more than thirty (30) days before the last day on which the customer may stop the renewal.
Changing an order
A change to a license (its plan, Monthly Users, billing period, or a move into a package) is made by a new Order that names the Order it amends and lists only what changes; everything else stays as it was, including the term, renewal and cancellation terms, the domains and the keys (an offline license gets a new key file to deploy). An upgrade costs the difference between the new and the current price for the days left until the next charge date, charged by card or invoiced as the Order states, and applies once that is paid (or, under invoice billing, when the Order is signed); a signed upgrade to be paid by card that is not paid before the offer expires lapses. A downgrade applies from the next charge date after the Order is signed, and nothing is charged or refunded. A change of billing period applies from the next billing date after the Order is signed, except that a license paid a year ahead switches when its paid year ends. An Application leaves a package only when an owner removes it in the console; it ends twenty-four (24) hours later, with no change of price and no refund.
What governs it
Each Order prints: "This order is governed by the Kernstra Web SDK License Terms, version [version], which the Customer accepts by signing this order. Use of the SDK by or for other companies, including resale or redistribution, needs a separate license." The current version is 2026-11, and it incorporates this page in the version in force on the day the Order is signed.
The Order prevails over the License Terms for the commercial terms it states, and the License Terms prevail over the Terms of Service for the licensed use of the SDK. A license stays on the version of the License Terms its Order names until the customer signs an Order that names a later one.