Two surfaces, two jobs
webtunel.com is where accounts live: registration, credit, invoices, and task history. It changes on a marketing and product cadence.
super-proxy.webtunel.com is the runtime: queue, worker leases, stream keys, and GPU provider control. It changes on an operational cadence and absorbs load spikes.
Why not merge them
Merging would couple a high-churn runtime to the account portal, so a runtime deploy could risk the surface where customers manage billing.
Keeping them apart means the dashboard stays available even while the runtime is scaling workers up and down.
How they stay in sync
The dashboard reads task state, events, and artifacts the runtime records. The runtime enforces credit the account portal sells.
Users see one product; operations get two independently deployable systems.