Roadmap
The current focus is Tip. Once Tip feels stable, understandable, and useful based on creator feedback, the DiscordBot comes next. After that, StreamerBot follows as the larger workflow module.
Origin
The earlier local build shows where KALYIX started. It remains available, but it is no longer the product focus. Active work now moves through Tip, Web, overlays, alerts, and later bot integrations.
V1 and V2 may still appear as context, but the roadmap is no longer driven by those labels. What matters is what creators can actually use next.
Active focus
Tip is the first real product area. It covers creator pages, payments, goals, overlays, alerts, and a studio that improves through real feedback.
When Tip feels good enough for everyday use, the next focus is DiscordBot. StreamerBot comes after that because it reaches deeper into scenes, actions, and automation.
Active development path
Each stage should deliver clear value before the next one opens up. That keeps KALYIX from becoming a pile of loose ideas and lets the ecosystem grow step by step.
Step 1
Tip gets the most attention first. Creator pages, Studio, payments, goals, overlays, and alerts should work clearly in daily use. Updates come from the plan, but also from real feedback.
Step 2
Once Tip is in a good place, DiscordBot becomes the next focus. It should provide server counters, status, and simple community functions while using the same KALYIX data.
Step 3
StreamerBot comes after Tip and DiscordBot because it reaches deeper into actions, scene logic, triggers, and automation. It needs a stable base first.
Tip bundles the first productive creator features: profile, pages, goals, payments, overlays, and alerts. That is where the visible value for creators and supporters appears first.
These areas should not run around Tip. Tip edits and stores, while workers provide public URLs, alerts, and live output.
Tip should grow from real feedback. If a Studio workflow is unclear, an overlay is awkward in OBS, or a payment flow has too many steps, that becomes a candidate for an update.
That is why this roadmap is not a rigid feature checklist. Sequence matters, but feedback helps decide which improvements happen first.
DiscordBot comes after Tip because it benefits directly from the same data: KALYIX users, Tip users, status, counters, and later community signals.
The goal is not an isolated bot, but another KALYIX module using existing events and state.
StreamerBot follows later because it touches active workflows more deeply: scene logic, actions, triggers, and automations need a stable shared base.
When this step starts, overlay and alert workers should already be established as shared output paths.