Questions, answered.

Key-Warden is a software licensing and activation platform for independent software vendors. It issues activation keys, enforces subscriptions and seats, and verifies every licence with a cryptographically signed token - while you stay the merchant of record. See how licensing works for the plain-language version.

Every validation answer is an Ed25519-signed token. Your product embeds only the public half of your per-vendor signing key, so it can verify a licence locally and can never forge one. Seats, expiry, node-lock and revocation are enforced from the licence itself and take effect on the next check. The developer docs show the exact API and a 15-line offline verify.

Yes. You set an offline grace window and, within it, your software keeps validating against the signed token it already holds - no live connection needed. That makes Key-Warden practical for desktop apps, air-gapped installs and field devices, not just always-online services. The platform ceiling on the grace window is 7 days.

Seat limits count activations. Each distinct device is recorded as a one-way hashed fingerprint - the raw machine identifier is never stored; when the number of active devices exceeds the seat count, an online check returns a definitive seat_limit_exceeded.

Yes, on higher plans. Every validation runs two gates: gate 1 is your validation key - the X-Client-Key that authenticates your app to Key-Warden - and gate 2 is the buyer's licence. Holding several validation keys lets you rotate without downtime or keep separate keys per environment (production, staging) and per app. Allowance by plan: Launch 1, Studio up to 3, Enterprise unlimited. See the two-gate model in the docs.

Yes. Revocation causes the next validation to return a signed denial; expiry ends access when a term lapses; and node-lock binds a licence to its devices. All of it is enforced from the licence and applies on the next check - you do not need to chase down installations.

No. Code protection - obfuscation, string encryption and per-buyer watermarking - runs entirely in your browser; nothing is uploaded. Your private signing keys are generated and sealed in Azure Key Vault and are never handed out in plaintext.

You are. You are the seller of record - your name is on the invoice, and the customer relationship, support and tax obligations are yours. Key-Warden does not take a percentage of your sales: you pay for the platform (your plan plus activation packs) and nothing else. Checkout is processed through Key-Warden today and settled to you; paying into your own connected Stripe or PayPal account is on the roadmap. See pricing for the plans.

On Microsoft Azure, encrypted in transit and at rest, with strict per-vendor segregation: every vendor has their own signing key sealed in Azure Key Vault, and API credentials are scoped to one vendor only. Validation calls carry only what licensing needs - a licence reference, product code, a hashed device fingerprint, client version and a timestamp. The security & data page has the detail.

Activation keys and certificates are delivered by email (and optionally SMS) the moment payment clears. For products you host with Key-Warden, buyers receive signed, short-lived download links for the current build and previous versions from their own portal.

The Enterprise plan includes white-label branding - your name, logo, tagline and support link on the buyer-facing pages. Reselling, hosting or white-labelling for third-party customers is a separate OEM / reseller arrangement; talk to us before onboarding third-party customers.