Renewals and multi-year terms

What you will do: choose a term length and payment schedule, and know what happens when the term ends.

Term lengths

Subscriptions run for 12, 24 or 36 months. Longer terms carry a lower price per year. The price is locked for the term: it does not change until renewal, whatever happens to list prices in the meantime.

Payment schedule

Each term can be paid:

• Annually — one invoice per year of the term, at the start of each year.
• Upfront — one invoice for the whole term at the start.

Upfront payment of a multi-year term gives the lowest total; annual payment spreads the cost. The schedule is agreed when the subscription is created and is shown on Subscription.

Renewal

1. Renewal notices are sent to the billing contacts ahead of the term end, and Subscription shows the renewal date:

Renewal notice: <placeholder> before term end

2. Review capacity against Usage: renew as is, add capacity or reduce it.
3. Accept the renewal quote. The new term starts when the current one ends and the licenses continue without interruption.

The subscription.renewed webhook (see the API section once you sign in) notifies your tooling when a renewal is confirmed.

Not renewing

Tell XPLG before the term ends, or cancel a marketplace subscription in the marketplace. Licenses stay valid until the term end; afterwards deployments keep their data and configuration but licensed features stop. See How licensing works.

Renewal pricing

Renewal terms, including any cap on price changes between terms, are set out in your subscription agreement and shown on the renewal quote.

Renewal price cap: <placeholder>

Next: Getting help

Verify with XPLG engineering before publishing.