Overlay runner
Local overlay host with scene switching and basic transitions. Builds and delivers your overlays straight into OBS — no SaaS, no lock-in.
- Local web server for overlays
- Scene & source routing
- Config via simple JSON
Overlay toolkit, no platform lock-in
KALYIX
Local, modular overlay engine that ships to your OBS. Extensible via plugins; you keep control.
What is KALYIX?
Local overlay engine, not another website
KALYIX is your local overlay engine. You build overlays in plain HTML, CSS and JS/TS (or React), add bindings like {stream.title} or {music.current} – KALYIX renders locally, keeps data in sync, and ships to your OBS.
Local-first runtime
Overlays render on your machine. If a cloud service dies or some overlay SaaS has an outage, your scenes keep working. Config and state live in files next to you, not behind a login.
HTML & React bridge
Plain HTML overlays can read keys like {stream.viewers}, while React overlays can use a small bridge (hooks / signals) to subscribe to the same data. One source of truth, different ways to render it.
Polyglot plugins
Plugins are language-agnostic. Rust, Python, Node… as long as a plugin speaks the KALYIX API, it can join the party. That makes it easier to extend, experiment and share modules over time.
First creator preview
What the first builds aim to ship with
The early alpha builds are meant to be usable, but also to show how KALYIX thinks about overlays under the hood.
Signals & data
One place to consume Twitch, music and custom data. Exposed as simple signals your overlays can listen to – whether they are plain HTML or React-based.
- Twitch auth & basic events
- Now playing / generic data sources
- Shared state across overlays
Starter overlays
A small set of scenes you can use as-is or tear apart to see how KALYIX thinks about overlays.
- Just chatting & in-game layouts
- BRB / starting soon examples
- All built with the public API
Details for the alpha may shift – some smaller pieces might land a bit later. The goal is to keep the core usable rather than ship a huge, fragile bundle.
After the local-first alpha, focus shifts to plugins: polyglot, swappable, with clear interfaces. An optional server mode is much later — first we ship solid local builds and plugins.
Why KALYIX exists
A toolkit, not a walled garden
KALYIX is for people who like to tweak. It should feel more like a set of tools you can rearrange than a locked-in editor – modular by design and not interested in turning your overlays into yet another platform.
Built around your workflow
You have OBS — KALYIX is your local HTML overlay editor: build and render overlays locally, show chat and events, hook up your own bots/integrations locally. Launch OBS via a local path; API control later only where it truly adds value. No cloud requirement — cloud stays optional, focus remains local.
Modular, not monolithic
You can replace small pieces instead of throwing everything away. Use the starter overlays, or swap them out and keep the same data layer and plugins underneath. Over time, that should make experiments safer, not scarier.
Minimal data, clear intent
The engine itself doesn't need your life story to work. Local overlays stay local. For sign-ups and news, email is enough – no tracking pixels, no surprise “growth experiments” hidden in the background.
Stay in the loop
Get the first creator builds
KALYIX will start with a small group of streamers and builders. Drop your email and you'll get updates when early builds are ready – no spam, no random “partner offers”.