Offline licensing

Offline licenses let approved Sleev accounts run the local gateway almost entirely offline. After Sleev is installed and the license is applied, day-to-day use does not require browser sign-in, online account checks, tracking uploads, or usage-pattern sharing with Sleev.

Access is approved case by case. If the Licenses page says your account does not have access, contact support@sleev.ai and describe the installation you need to support.

When to use it

Use offline licensing for machines that cannot rely on browser sign-in or regular online account checks. It is useful for restricted networks, lab machines, jump boxes, and other limited-internet environments where Sleev should not share tracking data or usage patterns.

Offline licensing does not make your model provider offline. Your coding tool still needs whatever access and credentials its upstream provider requires, unless that provider is also reachable inside your environment. Installing or updating Sleev, creating a license, and renewing a license also require online access from whichever machine or browser performs those steps.

Create a license

  1. On the machine that will run Sleev, install the sleev CLI and run:
  1. The CLI creates or reuses a local installation identity and prints an activation request that starts with slv_act_. This is local cryptography, not a network call.
  2. Sign in to the website on any approved browser and open Dashboard, then Licenses.
  3. Paste the slv_act_... request, add an optional label, and create the offline license.
  4. Copy the returned slv_lic_... license and paste it back into the waiting CLI prompt. If you closed the prompt, run sleev auth license request again on the same machine and paste the license there.

Renew

Offline licenses expire because issued licenses cannot be revoked instantly while a machine stays offline. Renew before the expiration shown by the CLI or dashboard.

When the license is inside its renewal window, generate a renewal request on the same licensed machine:

Paste the generated slv_renew_... request into the matching license in the dashboard, then apply the returned slv_lic_... replacement on the same installation.

Limits and recovery

  • One offline license is bound to one local Sleev installation.
  • For multiple machines, generate one activation request per machine.
  • Copying only the slv_lic_... string to another machine will not activate it there.
  • If a machine is lost or needs to be rehosted, contact support. There is no self-service revoke/delete flow in v1.
  • Keep the CLI and gateway updated so they include the current offline-license public keys.

To remove the active offline license from a machine while preserving its local offline identity for future requests, run:

If applying a license succeeds but the gateway does not restart cleanly, restart the daemon manually:

Privacy

During licensed offline use, the gateway verifies the signed license locally. Request metrics used by the local UI are recorded locally on the machine. Sleev does not receive tracking data, request metrics, or usage patterns from licensed day-to-day gateway use.

Sleev does not store provider credentials. Your coding tool sends its provider credential with each proxied request, and the local gateway forwards it upstream unchanged.