Skip to content
Networks

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?
No. We supplement venue circuits where permitted — we never replace or bypass them, and we never touch venue pathways, dark fiber, or demarc without written permission. The venue circuit typically stays in place as the underlay, and we deploy a segmented overlay for critical systems on top of it. If a venue prohibits any supplemental network at all, the engagement stops at assessment rather than proceeding to an unauthorized deployment.
Do you handle attendee Wi-Fi?
Attendee Wi-Fi is an add-on, never the lead. Our hero product is the Critical Operations Overlay for registration, payments, production, streaming and staff. We do not lead with attendee Wi-Fi, and we do not compete as a "bring your own Wi-Fi" or cheaper-venue-internet provider. Where attendee access is in scope, it sits on its own isolated segment, separate from payment and production traffic.

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?
No — never. LGL operates at the transport layer and does not log, store, or process cardholder or attendee data. Our job is to move the right traffic on the right segment, reliably and securely, while keeping that data entirely out of our hands — it never touches or is stored by us.
What does your segmentation standard look like?
We deploy a documented, acceptance-tested segmentation standard that isolates payment, production, registration, attendee, contractor, and management traffic into separate security zones. Wired connectivity is specified first for payments, registration, production, encoders, and streaming. Before go-live, the pre-opening acceptance test verifies that segmentation holds, that WAN failover lands inside its target window, that critical-system redundancy is live, and that monitoring is reporting.
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?
Every deployment documents a connectivity resilience design: dual-WAN where venue policy permits, otherwise a single approved underlay with defined LAN and edge failover scope. Failover is tested before go-live as part of pre-opening acceptance — we don't ship untested failover into a live event. A core operating principle is zero severity-one incidents where failover procedures were not tested pre-opening.
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?
Yes. White-label delivery through production and AV partners and corporate venues is a primary channel. The corporate event organizer is typically the entry buyer; production and AV partners and corporate venues are the scale channel and where repeat revenue compounds. Your client sees one integrated event package — we own the network operations layer, with a responsibility and authority matrix on every quote naming venue, partner, organizer, and LGL ownership for authorization, pathways, labor, and escalation.
How is an engagement structured?
Every engagement is scoped in writing from the Risk Assessment, with a responsibility matrix, non-cancellable circuit provisions, and a defined change-order process. The flow is: Risk Assessment → written venue authorization → Critical Operations Overlay → monitor through teardown → post-event report. We don't publish public pricing; each event is scoped on its specifics during the risk assessment call.
Do you offer self-serve gear rental?
No. We do not drop off equipment without onsite engineering and an accountable operator behind it. The value is operated accountability — design, deployment, onsite engineering, monitoring, documented acceptance testing, and a post-event report — not a box on a pallet. Specialty gear is rented and config-sensitive core kits are owned, but every deployment is operated by LGL end to end, setup to teardown.
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.