Software licensing by LEXIRA

One integration. Every way to license.

Lite Licensing System is the lightweight way to license and protect your software. Integrate once, then license each customer the way that suits them: a hardware dongle, a network license server, a standalone license on a single machine, online activation, or a one-time use license. LLS manages seats, renewals and usage, whether your customers stay fully offline or connect over the internet.

Lite Licensing System mark
License models

Integrate once. License each customer their way.

One SDK call in your application, one server at the customer, and every licensing model your sales team will ever need. Switch a customer from one model to another without shipping a new build.

Hardware dongle

A hardware dongle on the customer's license server. Plug it in, and the server reads the licenses next to it. Nothing to activate, nothing to phone home.

Network license server

Floating seats on the customer's own network. Client applications check seats in and out over the LAN, and the server refuses the next one when all seats are taken.

Standalone license

A signed license file bound to one machine's fingerprint. Ideal for Linux hosts and for customers who would rather not wait for a dongle to ship.

Online activation

Issue and deliver licenses over the internet for customers who are connected, with the same seats, dates, and caps as every other model, and usage statistics you can see as well as the customer.

One-time use license

A license that is valid for a single run or a fixed window. Trials, evaluations, pay-per-use, and field service engagements.

Inside every license

One license carries all the terms

Whatever the model, the license your customer receives, on a dongle, as a file, or through online activation, defines what your application may do. You set the terms once; the server enforces them.

  • Editions you define, such as Basic or Premium
  • Seat counts, with caps per client type
  • Start and end dates
  • Renewals without a restart; clients keep their seats
  • A usage dashboard: licenses, seats in use, the last 30 days
  • Application IDs scoped to your vendor certificate
How it works

Four steps from SDK to paying customer

01

Integrate the client

Add the LLS client library to your application. It registers with the customer's license server, checks in on a schedule, and tells your app what the license allows.

02

Certify your vendor key

Generate a key that never leaves your company. LEXIRA certifies it once for your application IDs. From then on you issue every license yourself.

03

Issue a license

Pick the model for this customer: dongle, network, standalone, online, or one-time, plus any edition you have defined, such as Basic or Premium. Set seats, dates, and caps, issue the license, and deliver it by any channel.

04

Renew and watch usage

A renewal is a new license, or for dongle customers possibly a new dongle. Install it and clients keep their seats without a restart. With offline licenses, usage stays on the customer's own dashboard; with online licenses, you see it too.

Standalone licenses

Works where the internet doesn't

With a standalone license, LLS never contacts you or LEXIRA after the license is issued. The only exchange is a machine fingerprint going out and a signed license file coming back, by email, a USB stick, or a support ticket. Client applications talk to the customer's own server over the local network and nothing else.

A dongle needs no exchange at all: plug it in and the server reads it. Online licenses are the opposite case, activated and renewed over the internet, with usage visible to you. The fingerprint behind a standalone license is built from hashed hardware identifiers, so raw values never leave the machine, and it tolerates the changes a real IT department makes.

  • Signed chain for license files: LEXIRA root, your vendor certificate, your license
  • Client applications pair with the server through a one-time code; secrets never travel in clear text
  • Optional request signing, so the server only accepts calls from your application
Change on the customer machineStandalone license
Network card replacedKeeps working
Hostname renamedKeeps working
Disk restored from an image backupKeeps working
Motherboard replacedReissue needed
Operating system reinstalledReissue needed
License file copied to another machineRefused
Disk cloned onto other hardwareRefused
Pricing

Two ways to pay, one product

Start with zero upfront cost and move to a flat fee when your volume justifies it. Both tiers run the same server, the same SDK, and the same license models.

Pay as you grow

For indie developers and startups

No upfront cost. A small, fixed percentage on each license you sell.

  • All five license models
  • License tracking and the usage dashboard
  • Standard support
Contact us

Subscription

For established teams

A predictable monthly or annual fee, whatever your volume.

  • Unlimited license issuing
  • Advanced usage metrics
  • Priority support
Contact us

Questions we hear first

Does my application need an internet connection?

Not with a dongle or a standalone license. Client applications talk to the customer's license server over the local network, and after a standalone license is issued that server never contacts you or LEXIRA. Online activation is there for customers who prefer it, and the models can be mixed.

Who issues the licenses?

You do. Your vendor key never leaves your company. LEXIRA certifies its public half once for your application IDs, and from then on you sign every license yourself with the issuing tool.

Can I sell different editions of the same application?

Yes. A license carries an edition you define, so the same build can run as, for example, Basic or Premium depending on the license it finds. Your application gates features on the edition LLS reports, and an upgrade is simply a new license.

What happens when a customer's hardware changes?

With a dongle, nothing: the license travels with the dongle, so the machine underneath can change freely. A standalone license tolerates a replaced network card, a renamed host, or a disk restored from backup. A new motherboard or a reinstalled operating system needs a reissued license, which takes one new fingerprint and one new file. Copying the file to another machine is refused.

How do renewals work?

A renewal is a new license with a later issue date. With a standalone or online license, the customer installs it through the dashboard or by activation and the server reloads it: every client keeps its seat and its session, and nobody has to register again. With a dongle license, the renewal may require a new dongle.

Which platforms does LLS support?

The license server runs on Windows and Linux, and client libraries exist for several programming languages, so the integration fits whatever stack your application already uses. A web dashboard shows licenses, application IDs, seats in use, and usage over the last 30 days. If you would rather not run a server at all, online activation is hosted on LEXIRA's systems.

How do I get started?

Write to us and we will set you up with the client library, the issuing tools, and a license server for your first customer.

Stop building licensing yourself

Tell us how you sell your software today and we will show you how each of your customers maps onto a license model.

Contact us