Manual / Leviathan 1.3
Manual/Premium licensing

Premium licensing

How the Spiky entitlement works, what it unlocks, how revocation lands, and what happens when the license plane is unavailable.

Premium is a separate distribution of the BungeeCord and Velocity forks. The anti-bot engine is the same core; Premium bundles the private Spiky entitlement provider and unlocks the managed control plane features. The Free Trial does not use this provider.

What Premium adds

  • A managed Spiky license, server identity, and machine fingerprint.
  • Heartbeat visibility and signed validation payloads.
  • Remote kill and restore that lands within the revalidation window.
  • The AbyssLink entitlement, which Free Trial cannot activate.
  • Premium distribution delivery through the private release process.
The gate is not a stronger tierPremium does not secretly weaken or strengthen the anti-bot engine. The same protection core runs in both editions. $5 buys the managed control plane, not a different filter.

Configuration

leviathan.yml · Premium fields
license-key: 'LEV-...'
license-api-url: 'https://license.vertalt.my.id'
license-api-key: 'spky_...'
license-server-id: 'edge-eu-01'
license-fingerprint: '<stable machine fingerprint>'
license-public-key: '<optional pinned Ed25519 SPKI>'
license-revalidate-seconds: 60

The environment takes precedence over YAML:LEVIATHAN_LICENSE_KEY, SPIKY_API_KEY,SPIKY_BASE_URL, SPIKY_SERVER_ID,SPIKY_FINGERPRINT, and SPIKY_PUBLIC_KEY.

license-api-urlHTTPS control-plane origin; https://license.vertalt.my.id
license-public-keyOptional pinned Ed25519 public key (base64 SPKI DER)
license-revalidate-secondsDefault 60; minimum 15
license-server-idStable server id; defaults to hostname
license-fingerprintStable machine fingerprint; pin it if hardware ids change
Never commit a credentialKeys, fingerprints, response bodies, and exception messages are not displayed by the operator command and should not be pasted into an issue, screenshot, or repository. Use environment variables or a protected config file.

Lifecycle

The provider activates once, verifies every signed validation payload, sends a heartbeat to populate the Spiky fleet, and revalidates on the configured cadence. A missing or rejected entitlement keeps protection running; it only disables Premium features.

A Premium label alone does not prove that entitlement was verified. The runtime reports the edition, but the operator should verify the activation state and heartbeat in the control plane.

Kill and restore

A license kill or product kill in Spiky lands during a live session, within the next revalidation window (60 seconds by default, minimum 15). Restore is observed on the next tick. The control plane is not polled on the Netty event loop.

Failure behavior

Validation failure is fail-open for protection: warn, keep the core gate running, and disable the gated Premium features. It never calls System.exit. An AbyssLink control session closes when entitlement is lost, but ordinary proxy policy continues.

A license server outage is not a reason to lose the edge. It is a reason to check the control plane, the network path, and the clock.

Boundary

  • No self-serve checkout is implemented; license requests go through the studio contact form.
  • No recurring interval, refund policy, support tier, or SLA is stated here.
  • The license is US$5 per license; one tier.
  • Premium credentials are delivered privately, not in a public release asset.

Request a Premium license · Next: AbyssLink