How KALYIX works together
KALYIX is made of independent areas such as Tipp, Overlay, Alert, News, and later DiscordBot and StreamerBot. Each area should work on its own, but also connect when needed without forcing creators to repeat the same setup everywhere.
Core idea
Independent when needed, connected when useful
A creator should be able to use Tipp without touching bot integrations, News, or additional workers. Overlay and Alert should also be able to serve their own public output.
When several areas are used together, they should understand the same events, tokens, and state. A tip can move a goal, update an overlay, trigger an alert, and later inform DiscordBot or StreamerBot.
Why this matters
No repeated setup for every area
Creator systems become messy when every tool needs its own data, links, and settings. KALYIX should reduce that friction.
- an area can be used on its own
- workers serve their output without hidden Tipp side logic
- Tipp, Overlay, Alert, and News keep clear jobs
- one event can reach several areas
- tokens and state do not need to be maintained twice
- new modules attach to the same event flow
System boundaries
Why KALYIX needs clear areas
KALYIX should not force everything into one app. When Tipp, Overlay, Alert, and later bots have clear boundaries, each area stays maintainable and can still work with the others through events.
- each area maintains the same data again
- creators repeat links, tokens, and settings everywhere
- alerts and overlays live as hidden side logic inside Tipp
- new features create more special paths
- workers stay independent and own their output
- events connect areas when they should work together
- Tipp can edit and store without owning Overlay or Alert
- new modules reuse existing events instead of duplicate logic
What the product is aiming for
More connection, less repeated work
KALYIX should stay understandable in daily use: areas are separate enough to remain maintainable, but connected enough that creators do not repeat the same work everywhere.
A tool instead of a workaround
KALYIX should not feel like a collection of detours. The goal is a system that carries the workflow without creating a new special path for every output.
More control during live use
Overlays, alerts, Tipp events, and later bot actions should run through a cleaner flow. For users, that means less friction between editing, preparing, and going live.
Clear roles inside the system
Tipp, Overlay, Alert, News, DiscordBot, and StreamerBot each get clearer responsibilities. That makes KALYIX more modular instead of rewiring everything for each new extension.
How this works technically
One shared event flow instead of several separate worlds
For users this should feel simple. Behind it, roles need to stay clear: areas store or render independently, while events connect them where that makes sense.
- Tipp manages creator pages, goals, and settings
- Overlay serves static public output
- Alert processes dynamic events and renderer output
- News, DiscordBot, and StreamerBot can later own their own jobs
- events are created once and routed deliberately
- tokens and live data can be reused
- one area does not need to know every other internal detail
- later integrations can connect without rebuilding everything
Who this is for
For users, the result should feel simpler, not more complicated
Even though the technical side of V2 goes deeper, the result should become easier for users. The rebuild is not an end in itself. It is meant to produce a more stable and clearer product.
KALYIX is aimed first at streamers and creators who want more control over the editor, alerts, and the live workflow without depending on somebody else's platform logic.
- Windows first as the main platform
- Twitch first as the real platform priority
- local use before cloud lock-in
- clear product boundaries instead of a mixed old/new stack
What this unlocks later
More modules without more chaos
When areas are separated cleanly, new modules can be added later without rebuilding Tipp, Overlay, or Alert again.
DiscordBot and StreamerBot should therefore not become a second world. They should reuse the same events and state while adding their own jobs.
Next step
You can find the concrete build plan in the roadmap
This page explains the ecosystem behind KALYIX. If you want to see what gets built first, what follows next, and why Tipp comes before DiscordBot and StreamerBot, head to the roadmap.