Where KALYIX is heading

Testing & releases

When a version is published, there are already a few steps ahead locally – features are tested in real setups before they show up in a tag. But there's no illusion that everything can be covered: the moment more people use it, they will find edge cases.

Patches and bugfixes are not tied strictly to big versions. If a fix is ready, it can ship as its own update instead of waiting for the next feature milestone.

Data, storage & safety

With the beta, a first database layer comes in to store structured data: configs, plugin state, and other pieces that shouldn't just live in one-off JSON files. That makes migrations and backups easier and adds a bit more protection than "hope the file never breaks".

The focus stays on local-first: your data sits on your machine by default, with server/hosted options later for setups that want shared control.

Marketplace checks & trust

For the marketplace around 1.0, uploads won't just be thrown online. The system will run basic checks when something is uploaded: if an overlay or plugin clearly errors out, it will not be shown as public.

In the early phase, only a small, selected set of uploads will be enabled and get a visible "verified" label. Over time, checks and tooling can evolve based on how people actually use the marketplace.

Creators can choose between free and paid, with a planned 90 / 10 split (90% to the creator, 10% for infra and upkeep).

Multi-channel chat & control

From the beta on, chat isn't just text in a box. KALYIX is planned to handle multi-channel chat: your broadcast chat plus additional channels, with mod rights detected after Twitch login or configured manually.

Chats can be displayed merged or split, and you can decide whether a message should be sent to one channel or multiple at once. Chat-mode controls (emote-only, sub-only, slow-mode) and basic mod-actions on messages are meant to live in one place instead of clicking through several dashboards.

Saved presets make it easy to keep extra chats attached to a setup, so you don't have to re-enter them every time you start the stream.

HTML overlays, React & plugin keys

KALYIX doesn't force one stack. A simple HTML overlay can use keys like {events.new.follower.name}, while a React overlay subscribes to the same value via a small bridge. Plugins can bring their own keys and even ready-made components – overlays just consume them.

In the editor, multiple pieces like NewFollower, now-playing widgets and chat components can be combined into a single overlay entry. That overlay is rendered as one local HTML file and loaded into OBS via Browser Source – KALYIX handles data and state, the browser just renders.

<!-- overlays/new-follower.html -->
<div class="follower-banner">
  <span class="pill">New follower</span>
  <span class="name">{events.new.follower.name}</span>
</div>

// overlays/NewFollower.tsx
import { useKalyixSignal } from "@kalyix/react";

export function NewFollower() {
  const name = useKalyixSignal("events.new.follower.name");

  if (!name) return null;

  return (
    <div className="follower-banner follower-banner--animate">
      <span className="pill">New follower</span>
      <span className="name">{name}</span>
    </div>
  );
}