Licensing that fails in your favour.
Self-hosted software has a hard problem: the code runs on a server we don't control, and the licence has to mean something anyway. Here is exactly how we solved it — including the parts most vendors don't put in writing.
When in doubt, let it run.
Wrongly blocking a paying customer costs far more than wrongly allowing someone for a few hours. A blocked installation means your client's business stops, your phone rings, and your relationship takes the damage — over a network timeout.
So every uncertain case resolves the same way: network failure, our server being down, a corrupt cache file, an unreadable response. The product keeps working and retries quietly.
Four pieces, and why each one is there.
None of this is novel cryptography. It's standard building blocks arranged so that the common failures are harmless and the attacks are expensive.
A signed token, not a yes/no answer
When your installation checks in, it doesn't get back “valid: true”. It gets a token signed with our private key, carrying your plan, your limits and its own expiry. Your server verifies the signature locally with a public key baked into the SDK.
Why it matters: someone who hijacks DNS and points our domain at their own server still can't produce a valid licence. They'd need the private key, which never leaves our infrastructure.
Bound to the installation
The token carries the identity of the installation it was issued for. Copy it to a second server and verification fails there, even though the token is genuine and unexpired.
Why it matters: without this, one legitimate licence file could be cloned across every server in a hosting account, and the licence would be worth nothing.
Two clocks, not one
Every token carries a normal validity window and a longer offline grace window. Under normal conditions your installation refreshes well inside the first. If we're unreachable, it keeps running on the second and shows you a quiet warning in the portal.
Why it matters: an outage on our side becomes a notification, not an incident for your client.
Token lifetime that adapts
A settled, healthy licence gets a long token. A brand-new one gets a shorter one. A licence under review gets a much shorter one.
Why it matters: this is the honest answer to “how fast can you revoke?”. Short tokens everywhere would mean constant check-ins and an outage every time our service hiccups. So the speed of revocation is tuned to risk rather than promised as instant.
What we can see, and what we can't.
You are putting our software in front of your clients. You should know precisely what leaves their server — not a reassuring paragraph, an actual list.
The licence SDK is readable code in your installation. You can open it and confirm every word of this yourself.
Sent to us
- Licence key
- Domain the installation runs on
- Product version and SDK version
- Server IP, from the connection itself
Never sent
- Your clients' records, of any kind
- Database contents or backups
- User names, emails or passwords from your installation
- Files, logs or configuration
Most licences are approved in seconds. Some aren't.
Every licence issued on this platform is approved here — that's the point of it. The question is only whether a human needs to be involved.
Automatic
Payment captured, details consistent, nothing unusual. The key is issued immediately and you can start installing. This is the overwhelming majority.
Quick human review
Something needs a second look — an unusual order pattern, a mismatch worth checking. You're told immediately that it's in review, with a time commitment, rather than being left watching a spinner.
We ask you something
Occasionally we need one piece of information before issuing. You get a specific question, not a vague rejection, and the licence is issued as soon as you answer.
Adding your GSTIN to your organisation measurably improves this. A verified business identity is the strongest signal we have, and it moves most orders into the automatic path.
The ones worth asking a vendor.
What exactly gets sent to Vend when my installation checks in?
The licence key, the normalised domain, the product version and the SDK version. That's the whole payload. No client records, no database contents, no user list, no file listing — the licence check has no access to any of it, by design.
How often does it check in?
Roughly once a day under normal conditions. The token itself is valid for longer than that, so a missed check-in is a non-event. Nothing about your product's day-to-day performance depends on reaching us.
What if someone copies my licence key to another server?
It won't work. The token is bound to the installation it was issued for, so pasting it elsewhere fails the check even though the key itself is valid. You'll also see the attempt in your activation history.
Can you switch off software I've paid for?
A revocation is possible — that's what makes the licence meaningful — but it isn't instant, and we don't pretend otherwise. Because tokens are valid for days, a revoked licence stops working when the current token runs out, not the moment someone clicks a button. We'd rather tell you that than claim a kill switch we don't have.
What happens if my server's clock is wrong?
The SDK notices. It remembers when it last checked in, and if the clock jumps backwards by more than a few minutes it stops trusting local time and forces an online validation. Turning the clock back is the oldest trick for extending an expired licence, and it's a cheap one to close.
Is any of this obfuscated or encrypted on my server?
The licence SDK is readable code. We're not shipping an encoder that breaks on half of Indian shared hosting and leaves you unable to debug your own installation. Licence enforcement is cryptographic, not cosmetic: the token is signed, and a signature can't be forged by reading the code that checks it.