RZ

RadialZ system map

Internal reference — enter the team password

Incorrect password
Internal reference · Support team

RadialZ system map

The full customer journey — from landing page to a working app — and the infrastructure that runs it. This is the picture to keep in your head when handling support.

Click any node or card to see what it does and what can go wrong.
00 The whole system at a glance

Three connected zones. The dashboard at the bottom plugs into the same worker and records that run the live system.

Customer journey Landing page radialz.app Customer buys Shopify checkout Download & install app Behind the scenes Shopify fires webhook order paid, signal sent Licence worker Cloudflare, makes key three things happen at once KV storage source of truth Zapier log backup in Sheet Resend email key to customer Customer inbox Activate licence enter key, first launch Worker validates key checks KV, registers PC App is live sculpting in ZBrush Support dashboard Licence manager dashboard team support tool Look up Reset machines Generate key dashboard acts on the same worker & records the live system uses
01 The customer journey

What the customer actually experiences, start to finish.

›
›
02 Behind the scenes

What happens automatically the moment a customer pays. No human touches any of this.

›
— then three things happen at once —
›
The one rule to remember

The licence key always exists in KV storage and the Google Sheet the instant a purchase completes. So “I never got my key” is almost never a missing key — it’s a missing email. The fix is the Resend Email button, not a new key.

03 The support dashboard

The licence manager — your tool. It plugs into the same licence worker and the same records the live system uses, so every action takes effect on real customers.

›
04 Common tickets

The quick map from what the customer says to which button solves it.

“I never received my licence key”
Look up by email to confirm it exists, then Resend Email. Check spam.
“My key won’t activate / says too many machines”
Look up, check machine count. Reset Machines to free them up.
“I got a new computer”
Reset Machines (all), or remove one machine to keep the other.
Customer refunded or charged back
Revoke Key — stops it working. Reversible if they dispute.
Beta tester or comp / giveaway licence
Generate Key — then email it manually (no auto-email).
Anything needing a code change or refund logic
Escalate to Pablo — not a dashboard task.
05 What it’s built on

A plain-English rundown of the pieces, for context.

Electron
The RadialZ desktop app — built with web technology wrapped in a Windows program. Why it has a custom interface and still runs like a normal app.
Python
A small plugin runs inside ZBrush itself. It’s the bridge that actually loads a brush when the customer picks one from the radial menu.
Cloudflare
Hosts the behind-the-scenes infrastructure — the licence worker, the key storage, and the app update files.
Shopify
The store where customers buy RadialZ. A paid order automatically triggers key generation — no manual step.
Resend
The email service that delivers licence keys. Branded email sent from licences@mail.radialz.app.
Zapier + Sheets
Every key generated is also logged to a Google Sheet as a backup — a human-readable list of who has what.
Auto-updates
RadialZ updates itself. A new version uploaded to Cloudflare reaches customers automatically on next launch.
Licence worker
The brain of the licence system. Generates keys, validates them on launch, and powers every dashboard action.
RadialZ — internal support reference · keep in Notion