Once you're past your first Flow (see Getting Started if you haven't been there yet), this page covers everything about the account itself: which platforms you've connected, what plan you're on, who else can touch your automations, and where notifications show up.
A Flow can only react to what StreamWizard can see, and only act where it's allowed to. So the first stop is Connect Platforms in the sidebar. Every platform StreamWizard supports has its own card there (today Twitch, Discord and OBS Manager), and new platforms show up as new cards in the same place. However many there are, each one connects in one of a few ways:

| How a platform connects | What you do | Today, for example |
|---|---|---|
| π Log in and approve | Click Connect, log in on the platform, approve what StreamWizard may do | Twitch, Discord |
| π Invite our bot | Invite the StreamWizard bot into your space on the platform | Discord servers |
| π» Pair an app on your computer | Click Connect and follow along to link an app on your streaming PC | OBS Studio (OBS Manager) |
Each platform counts once toward your plan, however many accounts you add to it (see Subscription).
Most platforms connect the way you'd expect: Connect, log in, approve. From then on your Flows can act as you. StreamWizard asks for the basics first, and for anything extra only when you publish a Flow that needs it (running ads on Twitch, for example). See the publish check.
Every Command in a Flow runs as someone: its Executor. Depending on the platform, you can pick:
All of them are included in every plan.
On some platforms StreamWizard works through its own bot that lives in your space, like a Discord server. Connect your own account, then Invite StreamWizard Bot into each space you want to automate. From then on the bot does the work, so there's no Executor to pick.
What the bot may do is up to you, on the platform itself. On Discord it gets its own role: give that role the permissions your Flows need under Server Settings β Roles, or in a channel's Permissions tab. StreamWizard tells you when something's missing as you publish (see the publish check).
Some of what you want to automate runs on your own streaming computer, like OBS Studio. With OBS Manager connected, your Flows can react to OBS (you switch scenes, the stream or the recording starts) and control it (switch the scene, show a source, set a volume). Your Twitch category can follow your game scene, and your "Be Right Back" scene can start an ad break (see how).
There's no login for an app like this. For OBS, StreamWizard pairs through a small page you add as a Browser Source: click Connect on the card and follow along. All you need is the password from OBS's WebSocket settings, and OBS 30 or newer (Streamlabs Desktop isn't supported).
π The web address you add to OBS contains your OBS password. It's shown only once: keep it to yourself, and if it ever leaks, disconnect straight away. Lost it, or changed the password in OBS? Reconnect gives you a new one.
The card shows Active while StreamWizard can reach the app, and Error when it can't (OBS is closed, or the Browser Source is missing). The little refresh button checks again. These Flows only work while the app is running.
This is where the free trial from Getting Started turns into an ongoing plan. The three tiers scale with how much you're actually running:

| Plan | Who it's for | Price | Platform connections | Scheduled Flows | Retrieve nodes per Flow | File storage | Rate limit (events per hour / day / month) |
|---|---|---|---|---|---|---|---|
| Starter | New streamers and smaller channels β essential automation to simplify your workflow | β¬4.99/mo Β· β¬49.99/yr | 2 | 5 | 1 | 50MB | 500 / 2,000 / 16,000 |
| Creator | Growing creators expanding across more platforms who want additional features | β¬9.99/mo Β· β¬99.99/yr | 5 | 10 | Unlimited | 100MB | 1,000 / 6,000 / 72,000 |
| Pro | Established creators and high-traffic channels who need advanced features and support | β¬19.99/mo Β· β¬199.99/yr | Unlimited | 20 | Unlimited | 500MB | 3,000 / 24,000 / 384,000 |
All prices are +VAT/Tax β checkout adds whatever rate applies in your country. A Monthly/Yearly toggle switches between them (yearly saves 17%).
New accounts get a 30-day free trial β no card required β and that trial runs on Starter's limits, so you're testing the real product, not a stripped-down demo. You're not locked into Starter for those 30 days either: you can subscribe to Creator or Pro at any point during the trial, immediately, without needing to finish it first. Subscribe to any tier before the trial runs out to keep going without a gap β if it lapses with no active trial or subscription behind it, every one of your Flows gets unpublished (nothing is deleted) and the account can't use StreamWizard's services until you subscribe. Subscribing at that point picks everything back up as it was, so there's nothing to rebuild β just resubscribe before you need it working again.
The one thing that is required: StreamWizard needs an active trial or a paid plan before the rest of the product unlocks for your own account β there's no browsing around without starting one of the two first, even though starting costs nothing. The one exception: a Delegate invited onto someone else's account (see Shared Access below) can act on it under their plan, with no trial or subscription of their own needed.
Rough guide for which tier actually fits:
None of this is enforced by the product. It's just where people typically outgrow the caps in practice, and platform connections (below) tends to be the actual trigger, not this list.
The caps that tend to matter in practice:
Every plan also shares the same ceilings, which are rarely reached: up to 100 published Flows, 100 nodes in a single Flow, 50 custom Collectables, 50 alert groups, 50 alert sources, 50 text highlights, and 20 MB per uploaded file.
Every plan comes with an allowance of events StreamWizard will process for your account: a maximum per hour, per day and per month (the last column of the table above). Think of it as a fuel tank with three gauges.
The allowances are sized around a typical streaming routine at each tier, so a normal month fits comfortably:
| Plan | Hourly allowance | A typical stream | Streams per month |
|---|---|---|---|
| π± Starter | 500 | about 4 hours | 8 |
| π Creator | 1,000 | about 6 hours | 12 |
| π Pro | 3,000 | about 8 hours | 16 |
Bigger channels are simply busier every hour, so the hourly allowance grows with the tier (500, then 1,000, then 3,000). The daily allowance covers a full stream at that pace, and the monthly one covers a full month of streams. These are planning guides for the numbers, not rules about how long or how often you may stream.
This page also has your Affiliate Invite Link β a general invite link for anyone you want to bring onto StreamWizard. A natural moment to use it: right after you've built something you're proud to show off β a friend who sees a slick alert or a working Collectables economy in your chat is a lot more likely to actually try it than one who just hears about it secondhand.
If you run your channel solo, you'll probably never need this page. If someone else helps you build or maintain automations β a co-mod, an editor, a friend who's better at the Flow Builder than you are β this is how they get in without you handing over your password. It costs them nothing, either: a Delegate you invite doesn't need their own plan, and doesn't even need to start a free trial, to help manage your account.
Once you're a Delegate on another account, jumping into it takes one click: your profile picture, top-left of the sidebar, opens a list of every account you can act on β your own, plus each one you've been invited into β pick any of them to switch straight in. Your current role shows right there too, so you always know whether you're looking at your own account or acting as a Delegate. The same switch is available from Accounts you have access to above β each row there has its own switch button, handy when you're already on this page checking who has access to what.

The bell icon next to your name, at the top of the sidebar, is StreamWizard's own in-app notification feed β separate from anything your Flows send out to Twitch or Discord. Nothing to configure; it's just where the product itself tells you things.
Every notification falls into one of three tiers:

Worth knowing: a notification always names the exact Folder and Flow it came from, so a problem in a busy account with many Flows still points you straight at the one that needs attention β no guessing which automation misfired.
When a Flow can't finish a command in a connected app, the notification tells you which kind of problem it was, so you know where to look. With OBS, for example, it tells apart two cases:
Flows that act on a space where our bot lives, like a Discord server, get one more: if the channel or server a Flow points at belongs to someone else's StreamWizard account, or StreamWizard can't match it to any of yours, the Flow stops and the notification says so.
Flows that use Collectables can send one too: when Add collectable or Spend collectable gets an empty User ID, or Add collectable gets an ID nobody on that platform has, that one action is skipped, and the notification names the Flow and the Collectable.
The same notification for the same command doesn't come back while it's still unread, or within a day of the last one, so an evening with OBS closed won't flood your bell.
There's a Light mode / Dark mode toggle at the bottom of the sidebar on every page β a per-account preference, not tied to anything else on this page. Flip it any time.