Build notes
V1 legacy build: no guarantee, no assurance
The KALYIX V1 build linked here is not an active product and not a stable release. It remains visible only as a legacy and reference state so the previous path stays understandable. Both technically and in terms of content, V1 is no longer the development focus.
1. V1 is no longer an active product path
KALYIX V1 is no longer being developed as the real product line. The current direction is V2 with its own shell, a new core, and a modular runtime path.
The V1 build is intentionally provided only as a legacy build. This does not create any claim to further development, maintenance, feature work, or long-term support.
2. More of a tech demo than finished software
At this point, V1 is mainly a technical reference state and at most a tech demo. The build may work on an end user's system, work only partially, or not run at all.
There is no assurance that the build will stay usable in a specific setup, on a specific Windows version, or with a specific combination of OBS, Twitch, plugins, browser components, or drivers.
3. No guarantee, no support, no reliability promise
For V1 there is no guarantee of stability, correctness, compatibility, availability, or fitness for a particular purpose. This applies especially to production streams, business use, or setups where failures would be critical.
There is also no claim to support, hotfixes, bug fixes, security updates, compatibility adjustments, or continued consideration of old V1 structures as the project moves forward.
4. Use at your own responsibility
If you start the V1 build or integrate it into your own setup, you do so under your own responsibility. Backups, testing, protecting your own system, and the decision to use the build at all are entirely up to you as the end user.
If problems arise from use or non-use, such as broken configurations, local failures, data loss, stream interruptions, or other technical consequences, responsibility for using the legacy build stays with the end user. Where legally permissible, no liability is assumed for this.
5. Dependency on third-party components
V1 is built on a completely different technical stack than V2 and also depends on external components and services. Changes in Windows, OBS, Twitch, Tauri, webview components, or other dependencies can make the build unusable or limited at any time.
Changes made by third parties or platforms do not create any claims against KALYIX.
6. Recommendation before use
If you test V1 at all, do it with the expectation of a legacy build and not with the expectation of a dependable product. Do not use it as a trusted base for productive, business-critical, or otherwise sensitive scenarios.
If you want to understand the real development path of KALYIX, follow V2 and the current roadmap, not V1.