The licensing problem nobody talks about#
Every piece of commercial hosting software phones home. cPanel checks in with its license server. WHMCS validates your key against its cloud. Plesk, DirectAdmin, InterWorx — they all do it. And when that license check fails, the consequences range from annoying warnings to full service lockout.
This is a real operational risk. We've seen hosts lose billing panel access during a DDoS attack on their vendor's infrastructure. We've seen cPanel licenses expire at 3 AM because a timezone mismatch triggered an early validation failure. We've heard from resellers who couldn't provision new accounts for hours because WHMCS's API was unreachable.
When you're running a hosting business, your control panel and billing system are mission-critical. A licensing outage is a business outage.
Why we built an offline-first license model#
Salieno Core validates licenses differently. The short version: once activated, it keeps working even if our license server disappears entirely.
The longer version involves three layers:
Layer 1: Activation handshake#
When you first install Salieno Core and enter your license key, the binary contacts our license server over HTTPS. It sends your key, a hardware fingerprint (CPU, disk serial, MAC address — standard stuff), and your installation timestamp. The server responds with a signed activation token.
That token is a JWT signed with an Ed25519 key. It contains your license tier, expiration date, allowed feature flags, and a "grace window" value. The token is stored locally on your server in a file with restricted permissions.
Layer 2: Local validation#
Every time Salieno Core starts — and periodically during operation — it validates the token locally. It checks the cryptographic signature, confirms the hardware fingerprint hasn't drifted beyond a configurable threshold, and verifies the expiration date.
No network call happens during this step. The binary has the public key embedded at compile time. It can verify the token's authenticity and freshness entirely offline.
Layer 3: Background renewal#
In the background, Salieno Core attempts to refresh the token periodically. If the license server is reachable, it gets a fresh token with an updated expiration window. If it's unreachable, nothing breaks. The existing token remains valid until its own expiration date — which is always set well beyond the renewal interval.
The grace window defaults to 72 hours past the token's stated expiration. This means even if your renewal is overdue and our server goes down, you have three full days of continued operation before anything changes.
What happens when the license actually expires#
Let's be honest about the failure mode. If your license genuinely expires — you cancel, your payment fails, whatever — Salieno Core doesn't lock you out of your data.
Instead, it enters a degraded mode:
- Existing sites keep running. Nginx, PHP-FPM, DNS — nothing stops serving traffic.
- Billing continues processing. Your WHMCS or Blesta integration keeps working so you can collect payments and close out accounts.
- New account creation is disabled. You can't spin up new hosting packages.
- Admin panel shows a persistent warning. It tells you the license status and provides a renewal link.
We made this choice deliberately. Holding customer sites hostage because of a billing dispute between you and us is bad engineering and bad business. The degraded mode gives you time to resolve the issue without your customers noticing.
The tradeoffs we accepted#
This approach isn't free. We gave up some things:
No instant revocation. If someone's license needs to be terminated immediately — fraud, abuse, legal — we can't flip a switch and kill their installation. The 72-hour grace window is the minimum response time. We mitigate this with payment-side controls and abuse monitoring, but it's a real limitation.
Hardware fingerprinting is fuzzy. Server hardware changes. You swap a disk, add RAM, move to a new VPS provider. We use a scoring system rather than a hard match — if enough hardware identifiers change, the token needs re-activation. Set the threshold too tight and legitimate migrations break. Too loose and you're just doing honor-system licensing anyway.
Token theft is possible. Someone could copy a valid token to another server. The hardware fingerprint makes this harder but not impossible, especially in virtualized environments where hardware profiles are similar. We accept this as a cost of offline operation.
Why this matters for resellers#
If you're running Salieno Core on a VPS in a colo facility, your network path to our license server goes through your provider's upstream, through the public internet, through our CDN, and into our infrastructure. Every hop is a potential failure point.
Hosting infrastructure has surprisingly poor uptime guarantees for licensing traffic. Your VPS provider promises 99.9% network uptime. Our infrastructure targets 99.95%. But the combined probability of both being available simultaneously is lower than either alone. And that's before you account for transient DNS failures, BGP route leaks, or the occasional misconfigured firewall rule that blocks outbound HTTPS.
Offline licensing means your business doesn't depend on the health of that network path. It depends on the health of your own server — which is the thing you're already monitoring, backing up, and maintaining.
The broader principle#
This isn't just about Salieno Core. It's about how self-hosted software should work in general.
When you choose to self-host, you're choosing operational sovereignty. You're saying: I want to control my own infrastructure, my own data, my own uptime. A licensing system that requires constant cloud connectivity undermines that choice. It reintroduces a single point of failure that you don't control.
We think commercial software can protect its revenue without compromising the operational independence that makes self-hosting valuable in the first place. Offline licensing is how we try to hold both of those goals at once.
0 comments
Loading comments…