Versioning your license payload: adding claims without breaking the clients already in the field
Zero Heartbeat
Designing a license key humans can type: base32, segment grouping, and a check digit that catches typos
Zero Heartbeat
License heartbeats and lease reaping: counting concurrent seats when clients crash
Zero Heartbeat
Designing a license gate: where to check, what to cache, and when to fail closed
Zero Heartbeat
Entitlements and Feature Flags, Driven by the License
Zero Heartbeat
Turning on license enforcement without locking out your customers: audit mode first
Zero Heartbeat
Deactivating a license and moving it to a new machine: receipts, offline proofs, and transfer limits
Zero Heartbeat
Licensing containers and autoscaled .NET services with Keyright
Zero Heartbeat
Trusting the clock: how licensing survives date rollback
Zero Heartbeat
Licensing a .NET CLI tool: headless activation, KEYRIGHT_LICENSE, and runners with no "Register" dialog
Zero Heartbeat
Logging a license check: structured events an operator can read, and never the key itself
Zero Heartbeat
Site licenses: binding one Keyright key to the customer''s domain instead of a machine, and what that binding can and cannot prove
Zero Heartbeat
Upgrade a self-hosted Keyright instance safely: migrations, zero downtime, rollback
Zero Heartbeat
Running Self-Hosted Keyright Across Multiple Nodes for High Availability
Zero Heartbeat
Back up and recover a self-hosted Keyright instance
Zero Heartbeat
Run self-hosted Keyright fully air-gapped, with no outbound internet
Zero Heartbeat
Rotating your license signing keys without locking out customers
Zero Heartbeat
Renewal nudges that don''t nag: driving "expires in N days" from LicenseKind, not a date in your code
Zero Heartbeat
Protecting your Keyright activation endpoint from abuse and key-sharing
Zero Heartbeat
One license key, three products: the product claim, suite bundles as entitlements, and the gate that lets a Lite key unlock Pro
Zero Heartbeat
Pinning your verification public key: the attacker who just swaps your key for theirs
Zero Heartbeat
One license, many clocks: per-entitlement expiry with Keyright
Zero Heartbeat
Verifying a Keyright license on Native AOT: no reflection, a trimmed verify path, and the public key as a ReadOnlySpan<byte>
Zero Heartbeat
License state as a health check: mapping a Keyright license onto Healthy, Degraded and Unhealthy without restart loops
Zero Heartbeat
Licensing a .NET component library: the developer license, the key that compiles into your customer''s app, and what the end user never sees
Zero Heartbeat