Home
Sign in

An on-prem license lets you run ORC8R on your own hardware without the demo ceilings. Your organization has one license key and one current subscription. You paste that key into the License tab of the self-hosted cluster you want licensed. This page covers buying, changing or cancelling the subscription, replacing the assigned cluster, and looking after the key.

If you are looking for how the licensed server behaves — the ceilings before a key is entered, the renewal and grace timeline, and what the server sends home — that is covered in the self-hosted server's own documentation, which every ORC8R server publishes at its /docs.

Buying a license

  1. Sign in to your ORC8R account and open the pricing cards, then switch to On-prem. Each card shows a plan's monthly price, its active-node cap, and what it includes. (Need more than the listed plans? The Custom card is an email to sales.)
  2. Choose a plan. Checkout creates the subscription for your organization's single on-prem license. For an existing subscription, use Manage plan on the Billing page.
  3. When payment is verified, you land on a success page showing the organization's license key, with a copy button. The key is emailed to you as well.

The subscription and key belong to the organization you selected before checkout. A purchase cannot be made anonymously or used to create an account automatically.

The license currently supports one cluster. A second machine cannot activate the key while the assigned cluster is still bound, even if that cluster is offline. Its existing binding and production renewal continue unchanged.

Changing or cancelling a plan

Plan changes and cancellation are self-serve from your organization's Billing tab at /orgs/{org}/billing:

  1. Open the organization and go to /orgs/{org}/billing.
  2. Use the subscription controls to upgrade, downgrade, cancel, or resubscribe.

Upgrades take effect after the upgraded payment is verified. Downgrades and cancellation take effect at the end of the paid period. Resubscribing uses the same organizational key.

What each one does to the licensed cluster:

  • Upgrade — after payment is verified, the new limits arrive with the next lease renewal, normally about 24 hours (with the renewal interval varying by ±10%).
  • Downgrade — the current plan remains in force through the paid period. The new limits arrive with a later lease renewal; the downgrade does not stop workloads already running.
  • Cancel — the current plan remains in force through the paid period. After it ends, a renewal is refused; the existing cluster then follows its lease and grace period before returning to demo ceilings. Workloads are never stopped.
  • Resubscribe or recover a failed payment — the same key remains associated with the organization and the cluster recovers on its next successful renewal.
  • Refresh — refreshing the license on the cluster's License tab renews the installed key without taking the license over from another cluster.

If a payment fails, the subscription is not cancelled straight away: Stripe retries on its own schedule, and your organization's owners are notified in the app and by email in the meantime.

On-prem management in Billing

Your organization's Billing tab at /orgs/{org}/billing shows the organization's license:

  • Plan and Status — the plan sold, and the state of its subscription (active, past_due, canceled).
  • The key, redacted to its first and last groups.
  • Assigned cluster — its hostname, cluster identity, server version, and when it last renewed. A key that has never been activated says Not activated yet.
  • Replace cluster — an authenticated replacement flow with a preview and explicit confirmation. Copy the exact Cluster identity shown in the target cluster's License tab, review the preview, and confirm before entering the same key on that cluster.

Seeing the page needs billing permission in the organization; revealing a key needs the permission to manage billing.

Looking after a key

A license key is a credential. Anyone holding it can try to activate a cluster with it, but a second machine is denied while the assigned cluster remains bound.

  • The console shows keys redacted. Reveal shows exactly one key, on the row you asked for, and only to someone who can manage billing.
  • Treat a key like an API token: do not paste it into a ticket, a chat channel, or a screenshot.
  • The self-hosted server seals the key in its secret store and never renders or logs it in full. Its binding persists while the cluster is offline.
  • If a key does leak, open a support request and we will revoke it and issue a replacement. Revoking turns the leaked key's renewals into an immediate refusal.
  • Billing & plans — plans and payment for ORC8R Cloud, which is billed separately from on-prem licenses.
  • Support — contact us about a license or a key.