Licensing models
How to sell software with Keygate: subscriptions, per-seat pricing, perpetual licenses with update periods, trials that move to a free plan, and team seats.
A product can be sold in more than one way at the same time. You might offer a monthly subscription, a yearly one and a perpetual license side by side, each with its own price and limits. In Keygate each of these is a plan.
Plans
Create plans under Plans in the dashboard. The settings that matter most:
| Setting | What it controls |
|---|---|
| License Type | subscription, perpetual or trial. The sections below explain each. |
| Billing Interval | Monthly or yearly, for subscriptions. |
| Max Activations | How many devices or users one license can be active on at once. On a per-seat plan this is Devices per seat. |
| Max Seats | How many people a license can hold, the owner included, for team products. 0 means no limit. |
| Sell per seat | Subscriptions only. The buyer chooses how many seats to pay for, between Minimum seats and Maximum seats. See per-seat pricing. |
| Grace Days | How long a license keeps working after its end date, to give a late renewal time to arrive. |
| Check-in Interval (days) | How many days your app may run offline before it must check in again. |
| Stripe Price ID | The Stripe price a customer pays for this plan. |
| When the trial ends, move to | Trial plans only. A free plan the license moves to when the trial ends, instead of expiring. See moving a trial to a free plan. |
| Self sign-up | Lets visitors claim a free license from the plan's link. See self sign up. |
| Features | What the plan unlocks. See Features and usage limits. |
Every plan also gets a checkout link of its own, which is how customers buy it. The Stripe guide covers that part.
Subscriptions
The customer pays every month or every year, and the license stays valid as long as they do. Keygate follows the subscription in Stripe: a renewal moves the license's end date forward, a failed payment marks it past due, and a cancellation lets it run to the end of the period already paid for.
Your app does not need to know about any of this. It asks whether the license is valid and gets a yes or a no, along with the date the license currently runs to.
Per-seat pricing
A subscription plan can be sold per seat: the buyer chooses how many seats to pay for, and the license holds that many. Use it when your price is per user, or per machine.
Setting up a per-seat plan
- Turn on Sell per seat when you create a subscription plan. It is not offered on perpetual or trial plans, and it is fixed once the plan is created: to sell the other way, create a new plan.
- Set Minimum seats and Maximum seats, the range a buyer can choose from. They start at 1 and 100, and the maximum can be at most 10,000.
- Set Devices per seat, or Concurrent sessions per seat on a floating plan. A license holds that many for each seat bought, shared by everyone on it.
- Max Seats is not used: the seats bought are the license's seat limit, the owner included.
What the seats buy depends on the product type:
| Product type | What the seats buy |
|---|---|
| SaaS | People: a license with 5 seats holds the owner and four members. |
| Hybrid | People, as for SaaS, and devices: devices per seat times the seats, shared by everyone on the license. |
| Desktop | Devices, or floating sessions: devices per seat times the quantity bought. There are no team members. |
Choosing seats at checkout
The plan's checkout link opens Stripe Checkout at the plan's minimum, and the buyer can change the number on Stripe's page within the plan's range. To start at another number, add it to the link, for example /pay/k3x9q2mf?quantity=5; a number outside the range is refused. The license holds what the subscription bills.
A free license that is upgraded to a per-seat plan starts with a seat for everyone already on it, or the plan's minimum if that is higher. The upgrade is refused when the license has more people than the plan's maximum.
Changing the number of seats
- Billed by Stripe: the owner uses Change seats in the customer portal, which shows the price before anything changes. Stripe is the record of the quantity: a change made in Stripe itself reaches the license too.
- Not billed by Stripe, for example a sale made elsewhere: an admin edits Seats bought on the license page in the dashboard, within the plan's range. Licenses billed by a Stripe subscription cannot be changed there.
- Lowering the seats is refused below what the license uses: its people, counting the owner and pending invitations, and its devices, or floating sessions on a floating plan. Nothing is removed by a change of seats, so the customer removes members, cancels invitations or frees devices first.
- Each change sends the
license.quantity_changedwebhook.
Seats lowered in Stripe itself are not checked this way. If that leaves the license with more people than seats, the members who joined last are paused until a seat is free.
Perpetual licenses
The customer pays once and owns the license for good. It has no end date and never needs renewing. This suits apps people buy the way they used to buy boxed software.
Perpetual with an update period
This is the model JetBrains made familiar. The customer pays once and keeps the version they have forever, but new releases are only included for a period, typically a year. After that the app keeps working; it just stops receiving updates until the customer renews.
To set it up on a perpetual plan:
- Set Updates Included (days) to the length of the update period that comes with a purchase, for example 365.
- Set Renewal Length (days) and a Stripe Renewal Price ID, a one time price, so customers can extend the period from the customer portal.
Each license then carries an updates_until date. Keygate's update feeds and download endpoint only offer releases published before it, and the signed token your app receives carries the same date, so the app can enforce it too.
Trials
A trial plan gives full access for a set number of days, then stops. There are two ways to use it.
- Free trial without payment. Issue trial licenses from the dashboard or from your backend through the admin API. When the days run out, the license expires and your app sees it, unless the plan names a free plan to move to.
- Trial that turns into a subscription. Sell the plan through Stripe with a trial period. The customer starts on the trial, Stripe charges the card when it ends, and the license becomes an active subscription. If the charge fails, the license goes past due like any other subscription.
A trial billed by Stripe is Stripe's to end. Stripe's charge and its report can arrive some time after the trial's end date, so Keygate waits for it for the plan's grace days, at least one day, before it expires the trial. Whether the key works in that time follows the grace days: with 0 grace days it stops at the trial's end until Stripe reports the payment.
A trial that expired can be given more time: set a new end date on the license in the dashboard and it starts working again.
Moving a trial to a free plan
A trial plan can name a free plan that its licenses move to when the trial ends, instead of expiring. The customer keeps using your app on a free tier with the same key, and can still upgrade to a paid plan later. Choose the plan under When the trial ends, move to on the trial plan. The default, Nothing (the trial expires), keeps the old behavior.
Which plans can be chosen
Only a plan that hands out nothing you sell qualifies. It has to be:
- a plan of the same product;
- free: no Stripe price, no update period and no renewals;
- not a trial plan;
- not sold per seat.
The plan does not need to be active, so you can keep the free tier off sale while trials still land on it. If no plan qualifies yet, create a free plan first, then come back and choose it.
What happens when the trial ends
- The license moves to the fallback plan and keeps its key. It becomes active, with no end date and no update period, and the fallback plan's features apply from then on. Add-ons on the license stay.
- Devices already activated keep working, but no new device can be activated beyond the fallback plan's Max Activations.
- On SaaS and hybrid products, members beyond the fallback plan's Max Seats are paused, the last to join first.
- The customer gets the trial ended email, from the Trial Expired template, where
{{.FallbackPlan}}names the plan. The reminders before the end, from the License Expiring template, say where the license moves too. See Emails. - The
plan.changedwebhook is sent withreasontrial_ended, instead oflicense.expired.
The move is made by an hourly check, shortly after the trial's end date. Until it happens, the key keeps working for at least a day past the trial's end, whatever the plan's grace days, so the customer is not locked out in between.
When a trial still expires
- The trial plan names no fallback plan.
- A Stripe subscription bills the trial. Stripe owns the plan of such a license, so it is left to Stripe as described under Trials.
- The fallback plan no longer qualifies when the trial ends. The dashboard refuses edits that would cause this, so it only happens after a change made directly in the database. The reason is recorded in the license's audit log.
Editing a plan used as a fallback
While a trial plan names a plan as its fallback, that plan must stay free, and it cannot become a trial plan or be deleted. The dashboard and the admin API refuse such a change with 409 TRIAL_FALLBACK_IN_USE and name the trial plans that use it. Choose another fallback on those trial plans first. A trial plan that changes to another license type drops its fallback.
Free licenses by self sign up
A free plan can hand out licenses on its own, for a free tier, a community edition or a trial people start themselves. Turn on Self sign-up on a plan without a Stripe price, update period or renewals. The plan's checkout link then opens a sign up form instead of Stripe Checkout:
- The visitor enters their email and receives a six digit code.
- They enter the code, and Keygate creates the license on that plan.
- The key is emailed the same way as after a purchase, and the visitor is signed in to the customer portal, where the license is waiting.
The link works without Stripe. On a trial plan the license starts as a trial of the plan's length. A license claimed this way can later be upgraded to a paid plan and keep its key.
Settings and limits
| Setting | What it does |
|---|---|
| Daily sign-up limit | How many licenses the plan hands out per day, counted from midnight UTC. 0 means no limit. When it is reached, the form tells visitors to try again tomorrow and no code is mailed. |
| Marketing consent checkbox | The label of an optional checkbox on the form, for example asking to receive product news. Leave it empty for no checkbox. |
- Each address gets one self sign up license per product. Claiming again, on any plan of that product, signs the visitor in to the license they already have, and the form tells them if it no longer works.
- A yes on the consent checkbox is stored on the license with the time it was given, and only for the wording the visitor saw: if you edit the label while someone has the form open, their answer is not recorded. The license page in the dashboard shows that a license came from self sign up and the answer.
- The
license.createdwebhook for these licenses carriessignup_sourceandmarketing_consent, so a mailing list or CRM can pick up new users. - The form mails codes under the same limits as the portal login: three codes per address every ten minutes, and
RATE_LIMIT_OTP_SENDper IP address per hour. It works even when sign ups are limited to emails that hold a license, since claiming the license is the sign up. See who can sign in.
Devices and seats
Not sure which limit fits your product? Node locked vs floating compares the options.
Device limits
Max activations caps how many devices can use one license at the same time. Activating a device the license already knows does not use another slot. When all slots are taken, a new activation is refused, and the customer frees one by deactivating an old device, either from your app or from the customer portal. On a per-seat plan the cap is devices per seat times the seats bought.
Floating licenses
If people share a pool of seats across many machines, use a floating license instead: any machine can take a seat, and the seat comes back when the app closes or stops checking in. See Floating licenses.
Team seats and members
For products sold to teams, max seats sets how many people a license can hold, counting the owner: a five seat license is the owner and four members. On a per-seat plan the seats bought set it instead. The product type decides which limit applies: desktop products count devices, SaaS products count seats, and hybrid products count both.
- The owner invites members by email from the customer portal, and removes them there. Only the owner manages the team.
- Every member who accepts an invitation gets a license key of their own, shown to them in the portal. It works like the license's key but keeps to the member's own devices, and it stops working when the member is removed.
- If a license ends up with more people than seats, for example after you lower a plan's max seats, the members who joined last are paused until a seat is free. The owner is never paused.
Customer portal and teams covers invitations, member license keys and paused members in detail.
License status
Every license has a status. Your app mostly cares whether the license works, and the table says when it does.
| Status | Meaning | Works? |
|---|---|---|
active | Paid for or issued, and in use. | Yes |
trialing | On a trial. | Yes |
past_due | A subscription payment failed and Stripe is retrying it. | Yes, while reminders go out |
canceled | The subscription was canceled. | Until the end of the paid period |
expired | The end date and the grace days have passed. | No |
suspended | Paused by an admin, or the subscription was paused in Stripe. | No, until reinstated |
revoked | Switched off for good, for example after a full refund. | No |
Active and past due licenses, and trials billed by Stripe, keep working for the plan's grace days after their end date. A canceled license stops exactly at its end date, since the customer chose to leave. A trial that Stripe does not bill ends at its end date: the hourly check expires it, or moves it to its fallback plan, in which case the key keeps working for at least a day until the move.
Changing plans
Customers who pay through Stripe change plans in the customer portal, for example from monthly to yearly, and see the price Stripe calculates before they confirm. A change that costs more applies once the difference is paid; one that lowers a limit, such as fewer seats or devices, applies at once and is billed from the next invoice. Changing plans and seats explains how each kind of change is billed. Customers on a free plan can upgrade to a paid plan from the portal and keep their key; see upgrading a free license.
For licenses that are not billed by Stripe, an admin can use Change Plan on the license page in the dashboard. Licenses billed by a Stripe subscription can only be changed through the customer portal or Stripe, so the two never disagree about what the customer is paying for. Change Plan follows these rules:
- Nobody is removed by a change of plan. A plan that holds fewer people than are on or invited to the license, counting the owner, is refused with
409 SEATS_IN_USE, unless the license was already that far over its old limit: remove members or cancel invitations first. - Moving to a per-seat plan from a plan that is not sold per seat gives the license a seat for each of those people, within the new plan's range. Between two per-seat plans the license keeps its seats, within the new plan's range.
- A license still on its trial that moves to a plan that is not a trial becomes active, and its trial end date is cleared.
Editing a plan is different from moving a license to another plan: a change to a plan's limits, such as max seats or max activations, applies at once to every license on it. Lowering max seats below what some teams already have pauses the members who joined last on those licenses, until a seat is free, and nobody new can be invited there. The dashboard asks you to confirm and says how many licenses that affects before it saves. To change the terms only for new customers, create a new plan and sell that one instead.
Frequently asked questions
Does the license owner count as a seat?
Yes. Max Seats is the number of people a license holds, the owner included, so a plan with 5 seats is the owner and four members. 0 means no limit. On a per-seat plan the seats bought count the same way.
What happens when a trial ends?
If the trial plan names a fallback plan, the license moves to that free plan with the same key, becomes active with no end date, and the free plan's limits apply. Otherwise the license expires. A trial billed by Stripe is left to Stripe, which charges the card and turns it into a subscription.
How do device limits work on a per-seat plan?
Devices per seat is multiplied by the seats bought, and the total is shared by everyone on the license. Ten seats on a plan with 2 devices per seat allow 20 devices, whoever activates them.
Can I turn an existing plan into a per-seat plan?
No. Whether a plan is sold per seat is set when the plan is created and cannot be changed, because licenses already sold on it were paid for the other way. Create a new per-seat plan and sell that one instead.
What happens if I lower Max Seats on a plan?
The new limit applies at once to every license on the plan. On licenses that already hold more people, the members who joined last are paused until a seat is free, and nobody new can be invited. The dashboard says how many licenses that affects before it saves.
Last updated October 26, 2026