Support is not an add-on when the show is live.
Zeus is sold as production infrastructure, and SpatialGen supports it that way: direct engineer access, deployment planning, delivery coordination, and a shared support channel with the people who understand the live workflow.
Live broadcast support has a different meaning than ordinary software support. When a production is live, the question is not whether a ticket has been acknowledged. The question is whether the people who understand the workflow are close enough to diagnose the problem before it becomes visible to the audience.
SpatialGen built Zeus around that reality. The system is not just a rackmount box with software on it. Zeus is a live ProRes 2110 workflow system for ingest, encoding, packaging, and distribution, and it ships with direct access to SpatialGen engineers because the hardest live workflows need both infrastructure and human accountability.
The Problem With Ticket-Queue Broadcast
Traditional enterprise support works through layers: first response, escalation, specialist review, vendor handoff, cloud-service investigation, and sometimes a separate systems integrator in the middle. That structure is wrong for live broadcast when a venue, truck, encoding system, playback format, and delivery path all have to agree in real time.
High-end live broadcast makes the support problem sharper. The team is not only moving video. It is moving high-resolution media with strict synchronization, metadata, audio, packaging, and device behavior. If something feels off, there may be several possible causes. Support has to understand the whole path, not just one service boundary.
Zeus support starts from the premise that the encoder, package, deployment, and customer workflow are one live system.
Direct Engineer Access
Zeus includes one year of direct SpatialGen engineer access. That matters because the people supporting the customer are not abstracted away from the product. They know the assumptions inside the system, the live workflow, and the demands of Apple Immersive Video and 4K live production.
The reservation flow sets the expectation plainly: after checkout, the SpatialGen team reaches out to schedule delivery and create a shared group chat with SpatialGen engineers. That group channel is not decorative. It reflects how high-stakes deployments actually get done. The customer needs a place to coordinate questions, timing, integration details, and event readiness with the people responsible for the system.
Support Begins Before The Event
The most valuable support happens before the first frame of the event. Zeus deployments should align around the customer’s camera plan, production rack, SDI or ProRes 2110 signal path, distribution target, expected resolution, frame rate, delivery bitrate, and operational fallback needs. For Zeus Lite, that means a 4K monoscopic live workflow with SDI support for traditional production teams. For the full Zeus system, that means a 16K-class immersive workflow on the same owned live foundation.
SpatialGen’s role is to make sure the system is not treated as a generic encoder dropped into an unfamiliar chain. Zeus exists because high-end live production is specialized. The support model has to be specialized too.
No Middlemen, No Mystery Layer
Support should not become another vendor integration problem. A common frustration in cloud live workflows is that accountability gets distributed across separate services. One provider sees contribution. Another sees encoding. Another sees delivery. Another handles support. Each layer can be healthy in isolation while the full event still struggles.
Zeus removes that ambiguity by putting the live workflow foundation inside a system SpatialGen controls and supports. Distribution partners and delivery paths can change by event, but the specialized ingest, encoding, packaging, and live workflow expertise comes from one team.
Support As Part Of The Purchase
Zeus changes the economic model, but it also changes the relationship. The customer is not buying temporary access to a cloud feature and hoping the meter stays reasonable. The customer is buying a system, a lifetime software license, and a support path built around repeatable production.
That distinction matters after the first successful event. The goal is not to relearn the workflow every time. The goal is to carry confidence forward: the same system, the same software foundation, the same engineering context, and a clearer path to the next broadcast.