Windows x64 · Open source. Try the demo or see how to use it on your stream.
The real interface in demo mode, with made-up data. Click the screenshots to enlarge them.
Meet Corneta
You keep building your scenes in OBS. Corneta receives that signal on your computer and sends it to the destinations you choose, while keeping the conversation and the story of the stream close at hand.
Video goes from your PC to the platforms. The Corneta website helps with setup and with signing in to integrations; it does not receive or relay your stream.
Before the stream: prepare each destination
Add platforms by URL and stream key, connect accounts where an integration is available, and check OBS and your upload before going on air. Custom destinations have a place too.
Choose how the signal reaches each platform:
| Mode | What it does |
|---|
| Straight up | Passes the OBS signal through without re-encoding the video. |
| Smart | Passes the signal through where it is compatible and adapts the destinations that need it. |
| All out | Re-encodes at the quality chosen for each destination. |
When available, GPU acceleration helps with processing. Each destination uses upload bandwidth; adapting the video also takes computer resources. Corneta shows estimates before the stream — actual capacity depends on your connection, machine and settings.
During the stream: the conversation stays close
Follow Twitch, YouTube and Kick chat in a single interface, with platform identification, emotes and moderation options depending on the integration. Chat and alerts can also open in separate windows.
A simulated conversation, with sources identified by platform.
The live panel tracks the state of each destination and the available OBS metrics. Per-destination reconnection, optional local recording and moment markers help you look after the stream without losing the thread of the conversation.
Streaming, sign-in and chat are separate capabilities. Sending video to a platform does not guarantee OAuth, chat, sending messages or moderation there. See the integration matrix.
After the stream: a story to revisit
The report starts with your stream: duration, available audience data, chat participation and marked moments. Charts show how it evolved; technical details get a chapter of their own, for when you want to dig in.
A 48-minute demo report, with made-up data and no video recording.
Recorded it? Rewatch the local video alongside the saved chat and jump between moments. Didn't record? The report still works with the data that was saved, without depending on a video. You can also export it to look at later.
Video and chat history are optional and off by default. Turn on what you want to keep before the stream; the replay depends on those files still being available on disk.
Try it without Rust, OBS or accounts
The shortest way to get to know the interface and start contributing is the browser demo. It uses made-up data and does not require connecting any account.
With Node.js 24.18.1 and pnpm 11.18.0 installed:
git clone https://github.com/pitroldev/corneta.git
cd corneta
pnpm install --frozen-lockfile
pnpm contrib:demo
Open http://127.0.0.1:1420. Explore stream setup, chat and the sample reports from the side menu.
The contributor profile does not load your personal .env and turns telemetry off. Do not copy real credentials or settings to try it out. The demo simulates streaming: it does not validate OBS, the encoder, the vault or real sign-in.
Use it on your stream
See the project releases for installers and release notes, and the changelog for every version in one place. Before running an installer, check it as described in the code signing policy and how to verify a release. Windows x64 is the current platform; macOS, Linux and Windows ARM do not have a validated distribution yet. Contributor builds are meant for development and do not replace the release installers.
To test the native app from source, follow the desktop development path below. Run your tests outside a real stream.
Develop and contribute
The desktop interface uses React, TypeScript and Tailwind CSS; the native app, Tauri 2 and Rust. The website and the setup API live in the Next.js workspace in web/.
You don't need to set up the whole project to help. Start with the area you want to improve and the contribution guide. Documentation, reproducible reports and interface tweaks count too.
Validate a contribution
In a clean clone, without .env, accounts or personal files:
pnpm contrib:check
This command validates the app and the website without the official operation's secrets. Additional requirements and native tests are in the development guide.
Website and local API — Next.js
pnpm contrib:web
Open http://localhost:7390. You can work on the website without configuring OAuth; signing in to real accounts requires configuring the providers.
The profile refuses real web/.env* files. If you already have a configured operation, use a clean clone — do not move or delete your credentials. For self-hosting and OAuth, see configuration and network contracts.
Native desktop — Windows x64
Besides Node/pnpm, install Rust 1.97.1, Visual Studio Build Tools with C++/MSVC and the Windows SDK, PowerShell 7 (pwsh) and the WebView2 Runtime. OBS with obs-websocket v5 is required to test the OBS integration.
pwsh -NoProfile -File scripts/fetch-binaries.ps1
pnpm contrib:app:dev
The script downloads and verifies the pinned versions of FFmpeg and MediaMTX. The first build compiles the Rust dependencies and is heavier than the demo; the time, memory and disk space it needs vary with the machine and cache.
To compile only the local executable, without creating or installing a distribution package:
pnpm contrib:app:build
The profile uses a separate contributor identity and vault, with the updater and telemetry turned off. OBS and network ports are still shared: do not test during a real stream. You do not need the official updater private key.
See development for the profile's limits. Packaging and distribution follow the release gates and signing, not the contribution flow.
Where things live
| Directory | Responsibility |
|---|
src/ | Desktop interface, design system, chat, reports and simulated engine. |
src-tauri/ | Native engine, OBS, media processing, vault and local persistence. |
web/ | Website, content and setup/OAuth API. It does not relay video. |
scripts/ | Development, validation and release preparation tools. |
docs/ | The project's maintained guides and contracts. |
compliance/ | Compliance inventories and evidence for the distribution. |
The media flow is local MediaMTX → Rust/FFmpeg processing → destinations, with per-destination supervision. Copying, re-encoding and shared processing depend on the mode and on compatibility. See the architecture for details.
Code, comments and documentation are in English. Issues can be opened in English or Portuguese. Before larger changes, start a conversation in an issue; for bugs, include reproduction steps with made-up data. Follow the code of conduct.
Documentation
The full index lists the other guides, including design, content, privacy and operations.
Privacy and security
Credentials use the native vault; recordings and reports stay on the computer. The screenshots in this README were taken in a disposable profile, with made-up data only — provenance and review of the images.
In the official distribution with telemetry configured, usage data is only sent after you explicitly turn it on; error reports are on when no earlier choice exists and can be turned off. The controls are independent and earlier choices are preserved. Turning on usage data does not send events from before it was turned on. Contributor builds disable sending. See the privacy policy for what is collected and the configuration for variables and kill switches.
Never post stream keys, tokens, .env, personal reports or raw logs in issues. Suspected vulnerabilities must go through the private security channel.
License
Corneta's own code is MIT. Dependencies, fonts, icons, models and sidecars keep their own licenses and notices: see THIRD_PARTY_NOTICES.md. Distributing FFmpeg also requires meeting the obligations of the binary used.
Forks are welcome, but must not present themselves as the official distribution or reuse its keys and services without their own configuration.
Try Corneta · Contribute to the project · Back to top
