Set up your overlays
The config hub installs your overlays, wires them to your channel and tells you when an update is out.
Everything runs in your browser. Tokens and passwords never go to the server.
What the config hub does
The config hub installs Twitch overlays for OBS and points them at your channel. It writes each overlay's widget.html into a folder on your own disk and puts a config.js next to it, which holds your channel name, your bot connection and the rules of the game.
It runs as a website in Chrome or Edge and needs no account and no installation. Credentials such as a StreamElements JWT or a Streamer.bot password go into that local config.js and never to a server.
Step-by-step, with pictures: Set up a Twitch overlay in OBS.
Common questions
Do I need a bot for the overlays?
No. Without a bot the overlays run on chat alone and you hand out points yourself. For automatic points you connect Streamer.bot, StreamElements or Firebot, and the hub fills that in during the connection step.
Which browser do I need for the config hub?
Chrome, Edge or Opera on a computer. Only those may write into a folder with your permission. Firefox and Safari run the same assistant, but it ends in a download you place yourself.
Can I set this up on my phone?
No, this is a job for your computer. OBS runs there and that is where the overlay files belong. From a phone you can send yourself the link and carry on at the computer.
What does it cost?
The config hub is free, and so is every overlay in the free group. The supporter overlays are not downloads, you request them.
What happens to my existing config.js?
Installing never overwrites it. It changes only when you press save in the hub, and keys the hub does not know are carried over unchanged.
Where do my token and my password go?
Into the config.js in your folder, nowhere else. The hub has no server that stores configurations. What an overlay later reports as anonymous usage statistics is described in the privacy policy.
How do I know an overlay is out of date?
The hub compares the files in your folder against the current build every time you open it and marks the row. An update replaces the widget.html only, your settings stay.