Skip to main content
Migrate Already selling? Move your customers to Keylight without re-issuing a single key.
Keylight

See what your licenses actually do

Stripe shows you revenue. It says nothing about whether licenses activate, keep validating, or quietly stop. Keylight measures the part after the payment.

Start Free
Activations & validations Active devices Monthly actives
Activations and validations
Every activation and every offline check, counted per day — so you can see adoption and drop-off, not just sales.
Active devices and MAU
How many devices are live right now and how many were active this month, across all your products.
Version and platform split
Break usage down by app version and by platform, so you know who's on the old build before you deprecate it.
No analytics SDK to wire
The signal rides the license activation and validation calls your app already makes. Nothing extra to instrument.

Updated August 2026

Revenue is only half the picture

Your payment provider tells you a sale happened. It cannot tell you whether the customer ever activated the app, whether their license is still validating a month later, or whether ten machines are quietly running one key. That second half — what happens after the payment — is where retention, support load, and piracy live, and it is exactly the part a Stripe dashboard is blind to.

Keylight sees it because every license check already flows through it. Turning those checks into numbers costs you nothing extra to instrument.

What you can see

  • Activations — how many devices came online, per day, per product.
  • Validations — how often apps re-check their license, including the offline checks that later sync. A flat line here is an early warning that something broke.
  • Active devices — how many machines are live right now.
  • Monthly actives — the honest “how many people actually use this” number, across every product in one place.

Each of these breaks down by app version and platform when your SDK reports them — the current Swift, Rust, JavaScript, C#, and C++ SDKs do — so you can answer “how many are still on 1.2?” before you drop support for it.

Nothing to wire up

There is no analytics SDK, no event schema, and no tracking code. The signal rides the activation and validation calls your app already makes to Keylight. You ship the license check; the charts fill in on their own.

Frequently asked

How is this different from my Stripe dashboard?+

Stripe knows who paid. It has no idea whether the app was installed, activated, or is still being used. Usage analytics measures the part that happens after checkout — activations, validations, and active devices — which is where retention and piracy actually show up.

Do I have to add an analytics SDK?+

No. The numbers are derived from the license activation and validation calls the Keylight SDK already makes. There is no separate analytics package to install, and no event code to write.

Can I see usage per app version or platform?+

Yes, when your SDK sends the app version, SDK version, and platform on activate and validate — the current SDKs do — the charts break down by each, so you can spot who is still on an old build.

Start licensing your app today

Drop in the Swift SDK, point it at your dashboard, and sell paid apps in under a minute. Free forever tier included.

Start Free