KALYIX

KALYIX

A creator system for tips, overlays, alerts, and stream workflows.

KALYIX is growing into a connected ecosystem for streamers and creators. Each area should work independently, but also connect cleanly with the others without duplicate setup or repeated imports.

Currently in progress: KALYIX Web, Tip Studio, Overlay Worker, and Alert Worker. The old local app stays visible as a tech demo, but it is no longer the main focus.

What KALYIX is

KALYIX connects the tools creators need around their stream.

The core idea is not one isolated app. It is a system of pages, workers, and editors. Tip, Overlay, Alert, News, and later bots should be usable on their own while understanding the same event flow.

Tip for creators

Tip is the first major product area: creator pages, goals, payments, links, icons, and an editor for public pages. Tip works on its own and can also feed overlays and alerts.

  • creator pages with a custom look
  • goals, tippers, and payment history
  • the base for alerts and overlays

Overlays and alerts

Overlays and alerts do not live as side logic inside Tip. They run through their own workers, so they stay independent while still accepting data from Tip, DiscordBot, or StreamerBot.

  • OBS-ready public URLs
  • static widgets and dynamic alerts
  • one shared path for stream events

Bot and community modules

DiscordBot and later StreamerBot should extend the system with counters, status, triggers, and automations without each module needing its own imports, duplicate settings, or separate logic.

  • Discord counters for KALYIX and Tip users
  • StreamerBot as a later workflow module
  • shared events instead of duplicate logic

Current and planned

Some parts are already usable, others are being prepared.

KALYIX should be clear about what exists and where it is going, without turning the landing page into a developer roadmap. The important part is what each area does for creators.

Now in focus

Tip Studio and live output

Tip, overlays, and alerts are the current focus. This is where the visible value appears: creator pages, OBS URLs, and live reactions to events.

  • Tip pages and creator profiles
  • overlay editor with public URLs
  • alert worker for dynamic events
  • payment and goal events as the base

Tip remains the first real product module. KALYIX Web is the entry point and will lead into the product areas cleanly.

Tech demo

The old local app stays visible

The previous local KALYIX app remains available as a test and reference state. It shows where the idea came from, but it is no longer the direction of the ecosystem.

  • Windows build as an old test state
  • useful for understanding the origin
  • no longer the focus for new features

If you only want to see the earlier state, this is the place. The new structure is being built in the web and worker system.

How the pieces connect

KALYIX should connect creator workflows, not scatter them.

The path is simple: creator foundation first, live output next, then bots and external workflows. Each module can run on its own, but uses the same event flow when several areas work together.

Base

Account, Tip, and creator page

Creators first need a place for their profile, links, goals, payments, and public page. Tip covers that area without forcing the same setup to be repeated elsewhere.

  • KALYIX account as the entry point
  • Tip profile as the creator area
  • public page for visitors and supporters

Live

Overlays and alerts for OBS

Live output runs through its own workers. Tip provides content and events, while Overlay and Alert independently handle the public output.

  • overlay URLs for static widgets
  • alert URLs for dynamic events
  • tokens and live data from one shared system

Extension

DiscordBot, StreamerBot, and more integrations

Later, more systems can use the same events: Discord counters, StreamerBot actions, community status, or external automation without rebuilding the same setup.

  • DiscordBot for server counters and status
  • StreamerBot for actions and scene logic
  • Bridge as the shared event path in the background

Public focus

Simple on the outside: kalyix.de, Tip, and Docs.

Internally, multiple workers and databases cooperate. Publicly, that should not feel technical. Users see KALYIX as the entry point, Tip as the creator product, and Docs as the help layer.

kalyix.de

The main domain explains the system and leads to account, updates, support, and the important product areas.

Tip

Tip is the creator area for profile, payments, goals, pages, overlays, and alerts.

Docs

Docs explain usage for creators and supporters without pushing internal worker or database terms to the front.

Community

Follow KALYIX on Discord

If you want to see what is being worked on, join Discord. Builds, tests, feedback, and next steps appear there more directly than through a public news list.

Discord is currently the best place for updates, feedback, and short looks at the build process.

Go to Discord

Who is behind KALYIX

Built by someone who looks at the ground first.

KALYIX is built by me, not by a large team and not from a perfect five-year plan.

I work on KALYIX because I see where tools slow people down, where processes become unnecessarily complicated, and where small gaps force large detours.

My focus is not to sound as big as possible. I want to find the places that block real work and close them in a way that actually works day to day.

Not pointing at the sky and saying: this is where we need to go. Instead, looking at the ground and saying: this is what is holding us back right now. Let us fix it.

KALYIX