CLOSED BETA

A second look at your live production design, before it reaches the venue.

Send an existing design or a plain-language brief. Zworykin works through it, shows its reasoning, and builds a handover package. Your engineer reviews and signs off.

Free closed beta. Your engineer signs off; Zworykin marks what it checked.

Named after the engineer who invented television.

Built for the engineers keeping it LIVE.

Zworykin is shaped by people who have had to make real shows work: broadcast engineers, sound engineers, directors, producers, and IP network specialists.

20

years in live television

What Zworykin designs

A connected engineering package from one brief.

Video signal flow diagrams

A clear first draft of the production's video path. Your engineer reviews the logic before it becomes the working plan.

Check my design

Audio routing plans

A practical routing draft for the show's audio needs. Built for engineering review, not generic AI output.

Send a brief

IP and hybrid architecture

A starting architecture for SDI, IP, and mixed workflows. Zworykin flags the assumptions your engineer needs to check.

Check my design

Equipment specification sheets

A working spec tied to the technical design. Your team adapts it to owned kit, rental stock, and project constraints.

Send a brief

How it works

From production brief to reviewed engineering pack.

01

Send the production brief

Describe the show in normal language: what needs to happen, what constraints matter, and what kit you plan to use. No template-heavy intake. Just the brief your engineer would normally start from.

02

Zworykin drafts the technical design

Zworykin generates a first-pass engineering package for your team to review. It also marks assumptions and points that need engineering judgment.

03

Review, refine, or take it forward

Your engineer checks the logic and adapts the design to the venue, crew, rental stock, and show risks. You can run the revised brief through Zworykin again for a cleaner version, or move straight into manual engineering work.

LIVE
SIGNAL FLOW AUDIO IP

Your engineer signs off — Zworykin gives a second look with reasons, and a package to hand over

Join the free beta

Built by broadcast people

Built by people who have had to make the show work

Zworykin comes from a team with 20 years in live television and media production. The team includes people who have designed broadcast systems, mixed live audio, built IP networks, worked inside OB vans, supported studios, and handled the gap between the production request and what can actually work on the day.

Broadcast engineers

They bring experience across TV channels, OB, studios, sports, corporate events, concerts, and temporary live production systems. They understand signal flow, routing, sync, redundancy, monitoring, playout, contribution, and the decisions that matter before a truck rolls.

Sound engineers

They bring broadcast audio knowledge across AoIP, Dante, AES67, console architecture, intercom, IFB, mix-minus, stage I/O, and record feeds. Zworykin treats audio as its own engineering discipline, not as a note under video.

Directors and producers

They bring the production view: what the client expects, what the director needs, and what the crew must understand quickly. They help Zworykin connect the technical design to the actual show, not just the rack room.

IT and network specialists

They bring IP broadcast infrastructure experience across ST 2110, NDI, Dante, VLAN planning, switch capacity, multicast, clocking, and failover. That matters because many live builds now sit between SDI habits and IP reality.

That is why Zworykin does not try to replace the engineer.

It gives the engineer a wider field of view: a first design draft shaped by broadcast, audio, IP, production, and network expertise — so they can review more options, catch risks earlier, and move faster into the right solution.

Why Zworykin

A second look with reasons, and a package you can hand over.

What others give you

  • Generic AI tools — They draw confident-looking connections without checking them against the equipment. A wrong cable or adapter looks as convincing as a right one, so you end up re-checking every line yourself.
  • Google, forums, and vendor manuals — They help with one device, one format, one question. They will not tell you that the diagram, the patch lists, and the equipment list have drifted apart.
  • A drawing from a similar show — A sound habit. But adapters, power, SFPs, and IP addresses are what change from show to show, and that is where small errors hide.

What we give you

  • A second look with reasons — Each point is marked as checked, an assumption, or an engineer's decision, with the reasoning shown. Nothing is presented as final.
  • Design and lists that agree — Signal compatibility, adapters, power, and IP conflicts are looked at across the same package, so mismatches show up before the site visit.
  • Handover with clear responsibility — Assumptions, open questions, and scope notes are written down for the client and the crew. Your engineer reviews and signs; Zworykin does not replace them.

Beta FAQ

Common questions

Does it cover audio as well as video?

Yes. Zworykin covers broadcast audio as a core part of the design, not as an afterthought. It can draft routing for consoles, AoIP, Dante, AES67, embedded audio, intercom, IFB, mix-minus, monitoring, record feeds, and program outputs.

Does it support IP and NDI workflows?

Yes. Zworykin supports IP, NDI, ST 2110, Dante, AES67, and hybrid SDI/IP workflows. It can help draft networked source and destination plans, switching assumptions, bandwidth notes, multicast considerations, and where SDI/IP handoffs need engineer review.

Can an AI produce something I would put on air?

Not without an engineer reviewing it. Zworykin produces a professional starting point: diagrams, routing plans, architecture notes, and specs that your engineer checks, corrects, and adapts to the project. It speeds up engineering work; it does not replace engineering judgment.

What happens in the closed beta?

You leave your email, we contact selected teams, and you send one real or representative live production brief. The beta is free and low-commitment. If selected, we ask what was useful, what was wrong, and what your engineer would change.

What will Zworykin cost?

The beta is free. We expect paid plans to sit in the range of a professional SaaS tool for small and mid-sized live production companies, likely priced around monthly use or per-design volume. Beta users will help shape pricing before launch.

Join the free beta

Send one design to check, or one brief to draft.

Free beta. No sales call required to submit interest.

We use your submission only for beta selection and follow-up. Analytics is optional and can be rejected below.