Pro license
What Rebutdesk Pro adds to a self-hosted server, how the license key activates and renews, and what happens when the check fails.
Everything in these docs works without a license. Paid add-ons come as license keys: Pro, and plugins such as IMAP mailboxes. Pro adds two things on top:
- Evidence templates by dispute reason. In a dispute case, Use template shows a checklist of what this reason needs and which of it the case already holds, drafts the statement from the case (payment, refunds, the buyer’s messages, tracking numbers found in messages and notes), fills empty evidence fields such as the tracking number or the PayPal evidence type, and ticks the timeline items worth attaching. Nothing is submitted; you review and edit as usual.
- Dispute reports. Reports gets a Disputes by reason table: won, lost and open by dispute reason and by processor, win rate and the amounts won back and lost, for 30 days, 90 days or a year.
On the hosted cloud, Pro is part of the Growth and Scale plans.
Getting the Pro build
Pro ships as its own build of the server, with the same settings as the open-source one (Configuration). Without a license it behaves exactly like the open-source server. Download it with the key from your purchase email:
curl -X POST https://app.rebutdesk.com/api/license/download \
-H "content-type: application/json" \
-d '{"key":"<your key>","artifact":"node"}' -o rebutdesk-pro-node.tar.gz
artifact |
Contents |
|---|---|
node |
server.mjs, the console, migrations, a Dockerfile, compose.yaml and .env.example, for Docker or any Node 24 server. |
worker |
A bundled worker.js, the console, migrations with migrate.mjs, and a wrangler.jsonc template, for Cloudflare Workers. |
Each archive has a README with the steps. To move an existing open-source install to Pro, point the Pro build at the same database and settings and add the key:
REBUTDESK_LICENSE_KEY=<your key>
With several keys (Pro and a plugin), list them separated by commas: REBUTDESK_LICENSE_KEY=key1,key2. Each key activates and renews on its own and shows as its own card on the Pro license page.
On Workers, set it with npx wrangler secret put REBUTDESK_LICENSE_KEY; the worker activates on its first cron run, within a minute.
How the license is checked
- On start (Node) or on the first cron run (Workers), the server activates itself for the host in
BETTER_AUTH_URLand receives a lease signed by Rebutdesk. The lease names the features and is valid for 30 days. - Once a day the server renews the lease. After a failed check it tries again every hour.
- If the license service cannot be reached, Pro keeps working until the current lease ends, so a network problem never switches it off for at least two weeks. The Pro license page shows the last check, the date the lease is valid until, and the last error.
- Each key allows a set number of servers. Restarts, redeploys and upgrades keep the same activation.
- A server at a different address that renews with another server’s activation, for example a staging copy of the production database, is not renewed: it activates on its own and takes a free activation, or reports that none is left. The original server is not affected.
- To move the key, open Pro license on the old server and click Deactivate this server: Pro stops there and the activation is free again. Activate on this server takes one again.
- Changing the key activates the server again; the old lease no longer counts.
- The server sends the key, its instance ID and its host name. No case or customer data is sent.
| Variable | Default | Meaning |
|---|---|---|
REBUTDESK_LICENSE_KEY |
none | Your license keys, separated by commas. Without any, paid features are off and nothing is sent to the license service. |
LICENSE_SERVER |
https://app.rebutdesk.com |
License service origin. |
Next: REST API and webhooks