Vaexcore, by JAMARQ
Vaexcore
Vaexcore, by JAMARQ: a streaming studio, a Twitch bot, a highlight finder and the hosted relay between them.
Began 2026-03-13 with Pulse, then called HighlightSmith, and grew to four apps by 2026-05-09. Carried the Tenra name from 2026-06-02 to 2026-10-02.
Why it was built
Studio exists to replace OBS on the owner's own streaming PC. The standing rule is that anything OBS offers, Studio offers or does better, in an app that also works with the rest of the line.
Pulse is about review time. A long recording hides a few good minutes, and Pulse suggests where they start and end, with a reason for each, for a person to keep or skip. It is not an automatic clip factory.
Vaexbot is a quiet Twitch operations bot without the usual clutter, and Relay is the hosted piece that holds the Twitch and Discord connections for it. The line keeps its own name because it serves creators rather than businesses, and it can stand apart from the JAMARQ apps.
At a glance
- Began
- 2026-03-13
- Status
- In use
- Runs as
- Tauri desktop apps for Studio and Pulse, Electron for Vaexbot, a hosted Worker for Relay
- Folded in
- Vaexpoint
What it does today
Built and working
Studio, the streaming studio
A scene designer, a GPU compositor, recording and multistream with an encode ladder per destination, chat and alert overlays, host and audio checks, and an importer for OBS scene collections.
Pulse, the highlight finder
Suggests clip boundaries in long recordings with reason codes. A review queue to keep, skip, defer, retime, split or merge, transcript correction, and exports for timestamps, YouTube chapters, shorts lists and edit decision lists.
Vaexbot, the Twitch bot
A desktop panel for chat commands, moderation, giveaways with an on-stream overlay, timers, Discord announcements, a go-live checklist, and a checkpoint queue for Destiny 2.
Relay, the hosted link
Holds the Twitch and Discord grants, takes Twitch events and Discord commands, and queues chat and alerts for Vaexbot. A cron retries every five minutes and a daily sweep clears old records.
How they connect
Twitch and Discord reach Relay, Relay queues for Vaexbot, Vaexbot feeds chat and alerts into Studio as scene sources, and Studio sends clips to Pulse. The installed apps update themselves from a public release feed.
How it came to be
The development cycle
340 commits and 146 merged pull requests for Studio, 142 and 45 for Pulse, 212 and 44 for Vaexbot, and 78 and 20 for Relay, as of 2026-10-05.
2026-03-13
Pulse: first commit, under the name HighlightSmith.
2026-04-28
Vaexbot: first commit, with a Twitch runtime and giveaways stored in SQLite.
2026-05-02
Studio: first commit. HighlightSmith was renamed Pulse the same day.
2026-05-09
Relay: first commit of the hosted Worker.
2026-05-26
Studio: a real output pipeline.
2026-07-02
Pulse: exports and search.
2026-09-01 to 09-02
Studio: Windows capture, NVENC encoding, one encode sent to several destinations, the OBS scene-collection importer, and a wgpu compositor.
2026-09-05
Vaexbot: a hosted mode that needs no local Twitch app credentials.
2026-09-08
Studio: Twitch chat as a scene source, fed by Vaexbot.
2026-09-12
Studio: shared encode, reconnect, crash-safe recording, split files, save the last 30 seconds, clip to Pulse, and an alert source.
2026-09-13
Studio, Pulse and Vaexbot: self-update from a public release feed.
2026-10-01
Vaexbot: Vaexpoint's checkpoint queue folded in, and the console renamed Vaexbot.
2026-10-02 to 10-03
Studio: a new logo and its own title bar. Pulse got a new logo the same week.
What was folded in
One app became part of this one
Earlier tools that did one piece of this job on their own. Their work moved here and their repositories were archived.
Vaexpoint
2026-06-27 to 2026-10-01
Its checkpoint queue became Vaexbot's Checkpoint Queue, with its own window and overlay. The standalone app was archived.
Where it stands
Real, and not yet
- •Windows x64 installers for Studio, Pulse and Vaexbot update themselves from a public release feed. They are not code-signed yet.
- •Studio records and streams through FFmpeg, to several destinations at once, with chat and alert overlays and OBS import.
- •Pulse's review queue, transcript correction, session library and exports work, and clips arrive from Studio.
- •Vaexbot runs chat, giveaways, moderation, timers and the checkpoint queue, with Discord announcements going through Relay.
Not built, or switched off
- There is no record yet of a full live broadcast run on Studio in place of OBS. Full OBS parity, connecting accounts instead of pasting stream keys, and per-track audio are still to come.
- Pulse's analyzer is intentionally lightweight, and its quality is the next piece of work.
- macOS builds are local only.
- A shared sign-in across the line has been agreed on but not built.
How it is built
Under the hood
The pieces
- Shell
- Tauri desktop apps for Studio and Pulse, Electron for Vaexbot, a hosted Worker for Relay
- Stack
- Rust, FFmpeg and wgpu in Studio. A Python analyzer and Fastify API in Pulse. Cloudflare Worker and D1 for Relay
- Platform
- Windows x64 installers that update from a public feed. macOS builds are local
- Data
- SQLite on the streaming machine for Studio and Vaexbot. Relay holds the Twitch and Discord grants
- Never
- Pulse never cuts a clip on its own. A person keeps or skips every suggestion
The service behind this
Need a tool like this for your own work?
Describe the job it would do and what you use today. You will hear back within one business day.