Frequently Asked Questions
Straight answers about mission-critical event networks.
How the Event Network Risk Assessment works, why we require written venue authorization, what we stand behind and what we don’t, how we handle payments and data responsibility, and how we deliver white-label. If your question isn’t here, get in touch.
The product
What LGL actually deploys — and what it deliberately is not.
What is a Critical Operations Network overlay?
It is our lead SKU: a segmented LAN with wired drops for payments, registration, production, streaming, and staff operations, deployed behind the venue circuit. It supplements venue circuits where permitted and never bypasses venue exclusivity. The point is isolated, monitored, accountable infrastructure for the systems that carry revenue and the event — not general internet for the building.
How is this different from venue Wi-Fi?
Venue Wi-Fi is shared, unsegmented attendee access with no single owner accountable for your revenue-critical systems. LGL is the opposite: one accountable operator instead of finger-pointing across venue, AV, payment, registration and carrier vendors — with wired-first critical paths, traffic segmentation, redundant connectivity, onsite engineering, NOC monitoring, documented acceptance testing, and an accountability scope defined in writing in the statement of work. We are an event-network operator, not an attendee-Wi-Fi vendor.
Do you replace the venue's internet?
Do you handle attendee Wi-Fi?
The Risk Assessment & venue authorization
How an engagement starts, and why authorization comes before spend.
What does the Risk Assessment cover?
The Event Network Risk Assessment is a free, documented evaluation that runs before any circuit orders or freight. It covers:
- Venue exclusivity and supplemental-network permissions
- Critical-application mapping and segmentation design
- Data-responsibility assumptions and payment-adjacent data flows
- Pathways, power, and RF assumptions
- A preliminary bill of materials and budget
- A go/no-go with a written venue-authorization path — or documented denial
Why do you require written venue authorization?
Venue denial is the single biggest risk to a deployment — a technically perfect network is worthless without permission. We obtain written venue authorization for supplemental network deployment before ordering non-cancellable circuits or shipping owned equipment. It protects you from sunk cost on a deal that can’t legally proceed, and it keeps us inside venue exclusivity rules. Deals without a viable authorization path stop at assessment, not deployment.
Where do you operate?
Our focus is corporate one-time events at mid-tier and production-controlled venues, where supplemental production networks are commonly negotiable. Tier-one stadiums and convention centers as launch markets are deferred. We deliver through a regional contractor bench under standardized runbooks, from regional hubs that follow anchor-partner demand.
Security, payments & accountability
How we segment traffic, where our data responsibility ends, and exactly what we stand behind.
How do you handle payments and data responsibility?
Every deployment touching payment or registration systems defines a data-responsibility boundary and shared-responsibility allocation among LGL, the partner, the organizer, the payment/registration vendor, and the venue before contract signature. We operate at the transport layer: we provide segmented network transport and operations only — we don’t run your payment or registration applications, and cardholder or attendee data never touches or is stored by us. Payment traffic rides on its own isolated, wired-first segment, separated from production, registration, attendee, contractor, and management traffic.
Do you store cardholder or attendee data?
What does your segmentation standard look like?
What do you stand behind — and what don't you?
We stand behind the network and transport we operate: availability, redundancy, and segmentation of the overlay, with failover on critical paths verified in documented pre-opening acceptance testing. We do not stand behind vendor application uptime — your payment, registration, or streaming applications are outside the network we operate. We also do not promise zero-risk absolutes; we promise documented, redundant, monitored connectivity, with our accountability scope defined in writing in the statement of work and a post-event report covering performance, incidents, and recommendations.
What about connectivity resilience and failover?
What about insurance?
Overlay contracts specify minimum cyber and E&O insurance coverage and breach-notification roles in the responsibility matrix before deployment execution. We carry — and require — appropriate coverage given that we operate payment-adjacent and production networks.
Working together
How partners embed LGL, and how an engagement is structured.
Do you work white-label?
How is an engagement structured?
Do you offer self-serve gear rental?
Do you only take multi-event work?
The entry point is a single corporate event, beginning with a Risk Assessment. That said, the repeat-revenue economics live in multi-event and white-label partner work, so we prioritize venue classes and partner relationships that compound. Production and AV partners and corporate venues running multiple events a year are an ideal fit.
Still have a question? Start with an assessment.
The Event Network Risk Assessment is free, and it converts into a call to scope deployment. Production and AV partners can embed LGL white-label.