Customer dashboards you are inthey see it, and can remove you — leave when the ticket closes
Recent activitythe eight latest — issues, changes, revocations and payments
Nothing has happened yet.
Licenses
Everything issued, who holds it, and what needs a look.
Nothing matches that filter.
Sales
Every payment the providers reported, newest first.
Paid, not redeemed means the money is in and the customer has not
pressed Redeem on Discord yet — a nudge usually solves it. Click a customer id to
see their licenses.
When
Customer
Plan
Amount
Via
Status
License
No sales yet. When someone pays, it shows up here.
Billing is off, so there is nothing to list. Turn it on under Billing.
Plans
What each tier delivers. This is the price list.
What each plan givesEach box is something a customer on that tier receives
Changes reach installed panels at their next renewal — up to 24 h, because
the list travels inside the signed key and the central cannot reach a panel behind NAT.
Emptying a whole column turns that plan off without revoking anyone's license.
A gold corner marks a box that differs from the factory default of that plan.
This installation cannot edit the price list: it has no signing key, so a change would never reach a panel.
Billing
Whether you are selling, and what it takes to.
Price and roleWhat turns billing on
What each paid plan costs, and the Discord role it grants. Leave a price empty to keep that
plan off sale in that currency — Mercado Pago charges in BRL, PayPal in
USD. The role is what the buyer receives the moment the money clears; the license
key is a second step they take themselves.
Provider keysLive in the hosting environment, never on this page
The five variables (MERCADOPAGO_WEBHOOK_SECRET,
MERCADOPAGO_ACCESS_TOKEN, PAYPAL_CLIENT_ID,
PAYPAL_CLIENT_SECRET, PAYPAL_WEBHOOK_ID)
are set in the hosting panel and need a restart. They are kept out of this page and out of
the backup file on purpose: a token inside a backup that gets shared is a leak. The status
band above tells you which ones are missing and where each one comes from.
Discord
The community the bot lives in.
CommunityLanguage roles for the bot, and the invite the site shows
The onboarding gives each member a language role. Paste the two role ids here and the
bot answers buttons in that member's language. Empty = English for everyone. The invite
link is what every "Open our Discord" button on the site opens.
The bot is off in this installation, so there is nothing to configure here.
Fleet
Every panel that ever paired, what it is running, and who went quiet.
Versions in the wildWho already has the fix that shipped
PanelsQuietest first — that is who you came here to find
Backup
The whole central is one file. Keep a copy; restore only on purpose.
Download a copyLicenses, servers, managers, shops, sales — everything
One JSON file, as it is on disk right now. The provider keys are not in it: they live in
the hosting environment. Keep the copy somewhere the hosting cannot lose.
Restore from a backupReplaces everything — irreversible
This replaces every license, server, manager and shop with the contents of
the backup file. A copy of what is here now is saved first, so a wrong file is recoverable.
Pick your gold-dash-backup.json — the impact is counted before
anything is written — then type RESTAURAR to confirm.
Daily snapshots
One a day, seven kept. Download one and drop it in the field above to restore from it —
it goes through the same impact check. These live with the service: they
protect against a wrong restore or a deleted license, not against losing the host. For
that, keep a manual download somewhere else.
Manage this licenseRevoke, archive, resend, support accessSigned keyReveals the key — anyone holding it can use the plan
The customer gets a one-time code. This is the key itself — it works
offline, on any machine, until it expires. Hand it over only when the code cannot.